PeopleSoft General Ledger 8.8 PeopleBook€¦ · Contents General Preface About These PeopleBooks .....xxv PeopleSoft Application Prerequisites.....xxv PeopleSoft Application Fundamentals.....xxv

PeopleSoft General Ledger 8.8 PeopleBook

December 2003

PeopleSoft General Ledger 8.8 PeopleBookSKU FSCM88GLR-B 1203Copyright 1992-2003 PeopleSoft, Inc. All rights reserved.

All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc. ("PeopleSoft"), protected by copyright laws and subject tothe nondisclosure provisions of the applicable PeopleSoft agreement. No part of this documentation may be reproduced, stored in a retrieval system,or transmitted in any form or by any means, including, but not limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise withoutthe prior written permission of PeopleSoft.

This documentation is subject to change without notice, and PeopleSoft does not warrant that the material contained in this documentation is free of errors.Any errors found in this document should be reported to PeopleSoft in writing.

The copyrighted software that accompanies this document is licensed for use only in strict accordance with the applicable license agreement which should beread carefully as it governs the terms of use of the software and this document, including the disclosure thereof.

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registered trademarks, and Pure Internet Architecture,Intelligent Context Manager, and The Real-Time Enterprise are trademarks of PeopleSoft, Inc. All other company and product names may be trademarks oftheir respective owners. The information contained herein is subject to change without notice.

Open Source Disclosure

PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability ordamages resulting from use of said software or documentation. The following open source software may be used in PeopleSoft products and the followingdisclaimers are provided.

Apache Software Foundation

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache SoftwareFoundation. All rights reserved.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALLTHE 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 ORSERVICES; 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 THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

OpenSSL

Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; 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 THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

SSLeay

Copyright (c) 1995-1998 Eric Young. All rights reserved.

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NOEVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Loki Library

Copyright (c) 2001 by Andrei Alexandrescu. This code accompanies the book:

Alexandrescu, Andrei. "Modern C++ Design: Generic Programming and Design Patterns Applied". Copyright (c) 2001. Addison-Wesley. Permission to use,copy, modify, distribute and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copiesand that both that copyright notice and this permission notice appear in supporting documentation.

Contents

General PrefaceAbout These PeopleBooks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvPeopleSoft Application Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvPeopleSoft Application Fundamentals. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .xxvRelated Documentation. . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .xxvi

Obtaining Documentation Updates. . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . .xxviOrdering Printed Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxvi

Typographical Conventions and Visual Cues.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviiTypographical Conventions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .xxviiVisual Cues.. . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . .. . . . .xxviii

Comments and Suggestions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxixCommon Elements in These PeopleBooks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxix

PrefacePeopleSoft General Ledger Preface. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiPeopleSoft Application Fundamentals. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .xxxi

Deferred Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxxiCommon Elements Used in This PeopleBook.. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .xxxii

Chapter 1Getting Started With PeopleSoft General Ledger.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1PeopleSoft General Ledger Business Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1PeopleSoft General Ledger Integrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2PeopleSoft General Ledger Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Chapter 2Navigating in PeopleSoft General Ledger... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Navigating in PeopleSoft General Ledger. . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .11

Pages Used to Navigate in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .11PeopleSoft General Ledger Business Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20PeopleSoft General Ledger Integrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Implementing General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

PeopleSoft Proprietary and Confidential iii

Contents

Chapter 3Defining Your Operational Structure... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Understanding PeopleSoft General Ledger Business Units and Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .25PeopleSoft General Ledger Business Units. . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . .26ADB Incremental Calculation Method.. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . .26Journal Processing Options for a Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .26VAT Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .27

Defining PeopleSoft General Ledger Business Units. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Pages Used to Define PeopleSoft General Ledger Business Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .28Defining a PeopleSoft General Ledger Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .28Defining PeopleSoft General Ledger Business Unit ID Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .29Specifying an ADB Incremental Calculation Method.. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . .29

Defining Journal Processing Options for a Business Unit. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .30Pages Used to Define Journal Processing Options for a Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .31Defining Journal Processing Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .31Specifying Balance Suspense ChartFields. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . .33Specifying Edit Suspense ChartFields.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .33Specifying Amount Suspense ChartFields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .34

Defining Currency Options for a Business Unit. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .34Page Used to Define Currency Options for a Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .34Defining Currency Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .34

Defining Approval Options for a Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Page Used to Define Approval Options for a Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .35Defining Approval Options.. . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . .35

Chapter 4Using Statistics... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Understanding Statistical Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .37Statistical Ledger and Accounts Method.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .38Statistics Code Method.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .38

Setting Up for Journal Entries Using Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Pages Used to Set Up for Journal Entries Using Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .39Setting Up for Journal Entries Using Statistical Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .39Setting Up for Journal Entries Using Statistics Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .39

Creating Journal Entries Using Statistics. . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .40Page Used to Create Statistical Journal Entries. . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . .40Creating Statistical Journal Entries Using a Statistical Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .40

iv PeopleSoft Proprietary and Confidential

Contents

Creating Statistical Journal Entries Using Statistics Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .40

Chapter 5Understanding General Ledger Background Processes. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43The Background Process Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Unit of Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .43Process Instance (Run ID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .44Request Records.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .44Message Log.. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . . .44

Initiation of Processes from Application Pages.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Restart and Recovery of Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Concurrent Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Concurrent Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .46Background Process Concurrency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .48

Chapter 6Integrating and Transferring Information Among Applications .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Understanding Enterprise Integration Points (EIP) in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . .63Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Creating Journals from Accounting Entries Using Journal Generator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Using Journal Generator with PeopleSoft Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .66Using Journal Generator with Third-Party Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .67

Integrating PeopleSoft General Ledger with PeopleSoft Applications. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .67Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .68Activating Integrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .68Publishing FullSync Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .73Publishing Sync Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .73Using Transaction and Other Messages.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .74

Integrating PeopleSoft General Ledger with PeopleSoft Enterprise Performance ManagementBudgeting. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .75

Page Used to Import the Enterprise Performance Management Budgeting. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .75Importing Data from Enterprise Performance Management Budgeting. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .76

Importing Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Importing Journals from Flat Files Using GL_JRNL_IMP .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .76Using Spreadsheet Journal Import (GL_EXCL_JRNL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .76Importing Commit Control Budget Journals Using Flat Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .77

Transferring Ledgers for Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Publishing and Subscribing Ledger Data. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .77Importing Information to a Ledger Using GL_LED_IMP.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .77

PeopleSoft Proprietary and Confidential v

Contents

Chapter 7Optimizing General Ledger Performance. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Understanding Optimal General Ledger Performance.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Using Non-Shared Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Pages Used to Set Up GL Non-Shared Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .80Using PeopleTools Temporary Tables. . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . . .80Using GL Non-Shared Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .80Setting Up GL Non-Shared Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .82

Using Indexes.. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Identifying Appropriate Indexes... . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . .86Selecting Indexes.. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . .87Making the Rules Practical. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .89Indexes in the Demo System.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .92Optimizing Indexes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .100

Using Partition IDs.. . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . .102Using ADB Incremental Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Updating Summary Ledgers Incrementally. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Optimizing PS/nVision Performance.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Tree JOINs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .105Combination Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .105Capturing SQL.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .106

Chapter 8Making General Ledger Journal Entries. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Understanding PeopleSoft General Ledger Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .107Journal Components and Processing.. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .108Journal Entry Identification and Masks.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .108Journal Entry Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .109

Creating Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Pages Used for Journal Entry. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .111Entering Journal Header Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .112Specifying Journal Entry Currency Default. . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .115Using the Exchange Rate Detail Page.. . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . .116Specifying Journal Entry Reversal Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .116Specifying Commitment Control Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .119Entering Journal Line Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .119Specifying Processing Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .123

vi PeopleSoft Proprietary and Confidential

Contents

Initiating the Calculate Amount Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .124Using Separate Debit and Credit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .126Retrieving a System Rate.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .127Entering an Exchange Rate Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .127Calculating Using the Calculate Rules. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .132Selecting a Journal Entry Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .135Setting Journal Entry Copy Down Options .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .137Entering Projects Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .137Accessing the Secondary Ledger Lines.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .138Using Statistics Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .139Specifying Journal Entry Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .139Viewing Journal Entry Errors. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .141Specifying Journal Entry Approval Options .. . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . .. . . . . . .142

Creating Inter/Intraunit Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143Pages Used to Make Inter/Intraunit Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .144Setting Up for Inter/Intraunit Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .144Creating Intraunit Journal Entries.. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .145Creating Interunit Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .146

Posting to Summary Ledgers and the Summary Ledger Staging Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Creating SJEs.. .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . . .147

Understanding SJEs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .147Pages Used for Creating SJEs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .148Defining SJEs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .148Setting Up Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .150Creating a SJE .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .150Viewing the Statuses of Standard Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .152Viewing the Amount Spread.. . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . .. . . . . . .153Running the Standard Journal Entry Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .153

Editing Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Copying Journal Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Understanding Copying Journals. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .154Pages Used to Copy Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .155Running the Copy Journals Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .155Defining Copy Journal Dates. . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . .. . . . . . .157Copying Journals Online. . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . .. . . . . . .158

Deleting Journal Entries Not Yet Posted.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159Using the Journal Entry Import Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Understanding File Format in the Flat File Journal Import Process.. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .160Page Used to Import Journals from Flat Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .170Importing Journals From Flat Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .170

PeopleSoft Proprietary and Confidential vii

Contents

Using the Spreadsheet Journal Entry Import Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .171

Chapter 9Using Spreadsheet Journal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Understanding Spreadsheet Journal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .173Spreadsheet Journal Import Overview.. . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . .174

Setting Up and Importing Spreadsheet Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175Pages Used to Set Up and Import Spreadsheet Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .176Using the Spreadsheet Journal Import Control Page.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .176Setting Up Workbook Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .178Creating a New Journal Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .182Entering Journals Using Journal Sheets. .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . .183Importing Journal Sheets in Online Mode.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .184Importing Journal Sheets in Batch Mode.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .185

Chapter 10Processing Journals. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Understanding Journal Processing.. . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . . . . .189

Common Terminology.. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . .189Journal Processing .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Journal Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .191Journal Posting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .192Unposting Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .193Changing the Unpost Journal Date for Business Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .194Journal Error Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .195Journal Error and Suspense Journal Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .196Suspense Journals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .197

Determining the Status of Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Pages Used to View the Status of Journals. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .197Viewing the Journal Header Information.. . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .. . . . . . .198Viewing Journal Line Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .199

Requesting Journal Edits. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200Pages Used to Perform Journal Edit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .201Running the Journal Edit Process .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .201Checking the Status of Edit Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .203Correcting Journal Edit Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .203Finding Journal Entry Errors . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .203

viii PeopleSoft Proprietary and Confidential

Contents

Posting Journals. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204Pages Used to Post Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .204Setting the Process Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .205Marking Journals for Posting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .206Running the Journal Post Process .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .207Checking the Status of Posting Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .208

Unposting Journals. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .209Page Used to Unpost Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .209Marking Journals for Unposting. . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . .. . . . . . .209

Correcting Journal Errors. . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .210Pages Used to Correct Journal Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .211Using the Journal Suspense Correction Option.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .212Selecting a Journal Line Display . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .214Reviewing Journal ChartField Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .215Changing ChartField Values ... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . .. . . . . . .215Changing Reversal Information for Correction Journal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .216Viewing Errors for Suspense Journal Correction Lines.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .218Inquiring on Suspense Cross References .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .218Posting and Unposting Suspense and Correction Journals. . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . .. . . . . . .219Unlocking a Journal Process Instance.. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .219

Producing Journal Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Pages Used to Produce Journal Reports. . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . .. . . . . . .221

Chapter 11Using Open Item Accounting... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223Understanding Open Item Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .223Open Item Accounting in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .223Common Open Item Terminology.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .224Open Item Prompt Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .224Reconcile and Close Open Item Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .224

Setting Up an Open Item Prompt Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Creating an Open Item Prompt Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .225

Entering and Processing Open Item Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225Pages Used to Enter and Process Open Item Transactions.. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .226Creating Open Item Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .226Processing Open Item Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .226

Reconciling and Closing Open Item Balances.. . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .227Pages Used to Enter Open Item Transactions.. . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . .. . . . . . .228

PeopleSoft Proprietary and Confidential ix

Contents

Using the PS/GL Open Item Reconciliation process (GLPPOITM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .228Using the Manual Open Item Reconciliation and Close Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .228Reviewing Reconciled Open Items.. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .231

Chapter 12Using Inter/Intraunit Processing in PeopleSoft General Ledger. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Understanding Inter/Intraunit Processing in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

Use of the Journal Edit Process to Initiate the Inter/Intraunit Processor Process.. . . . . . . . . . . . . . . . .. . . . . . .234Generation of Suspense Correction Journal Lines for Inter/Intraunit Transactions. . . . . . . . . . . . . . . .. . . . . . .234Inter/Intraunit Journal Copying.. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .235Creating Inter/Intraunit Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .235Creating Inter/Intraunit Allocation Journals. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .235Performing Inter/Intraunit Consolidations. . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .235Importing Inter/intraunit Journals Using a Flat-File Journal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .236Importing Inter/Intraunit Journals Using a Spreadsheet Journal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .236

Chapter 13Processing Value Added Tax (VAT) Transactions in PeopleSoft General Ledger. . . . . . . . . . . . .237Understanding PeopleSoft General Ledger VAT Setup and Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .238VAT Default and Override Relationships in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .238VAT Setup and Defaulting for PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . .240VAT Transaction Entry and Processing in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .241

Setting Up VAT Options and Defaults for General Ledger Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Pages Used to Set Up VAT Options and Defaults for General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .244Setting Up VAT Defaults for the General Ledger VAT Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .244Setting Up General Ledger Business Unit VAT Default Options .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .246Setting Up VAT Default Options for Journal Source .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .247Setting Up VAT Defaults for an Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .248

Creating and Processing Journals with VAT.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249Pages Used to Create and Process Journals with VAT.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .250Entering VAT in the General Ledger Journal Lines.. . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .. . . . . . .250Updating VAT Data in the General Ledger Journal VAT Lines.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .251

Importing VAT Data from Third-Party Systems.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Page Used to Import VAT from Third-Party Systems.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .254Importing VAT Journals Using GL_JRNL_IMP.. .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .. . . . . . .254

x PeopleSoft Proprietary and Confidential

Contents

Chapter 14Calculating Average Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255Understanding Average Balance Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .255Common Elements Used in This Chapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .258Average Daily Balance Setup.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .258Summary of Capabilities. . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .258Ledgers Used by ADB.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .258Average Balance Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .259How ADB Determines Calculation Method.. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .259Incremental Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .260Ad Hoc Calculations. . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .262Adjustments in ADB.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .263Period 998 Adjustments in ADB.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .264Management versus Regulatory ADB Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .265

Preparing Your System for Average Daily Balancing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Pages Used to Set Up Average Balances.. . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . .. . . . . . .267Identifying the Ledgers. . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .267Identifying Rounding Adjustments. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .269Identifying the ChartFields. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . .. . . . . . .270

Processing Average Daily Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272Understanding Processing of ADB.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .272Page Used to Process Average Daily Balances.. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . .273Requesting the Average Daily Balance Process .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .273

Producing Average Daily Balance Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Understanding ADB Report Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .275Pages Used to Produce Average Daily Balance Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .276Running the ADB Definition Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .276Running the ADB Calculation Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .276

Chapter 15Processing Multiple Currencies in PeopleSoft General Ledger.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Overview of Multiple Currencies in General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Preparing to Revalue Account Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Defining Revaluation Steps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

Pages Used to Define Revaluation Steps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .280Specifying a Ledger and TimeSpan for Revaluation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .280Specifying Source ChartFields for Revaluation. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . .281Specifying Output and Journal Options for Revaluation. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .282

PeopleSoft Proprietary and Confidential xi

Contents

Specifying Gain and Loss ChartFields for Revaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .286Preparing to Translate Ledger Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287Setting Up Translation Rules. . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .288

Pages Used to Set Up Translation Rules. . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . .. . . . . . .288Defining TimeSpans and Rates for a Translation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .288Defining ChartFields for a Translation Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .289

Defining Translation Steps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290Pages Used to Define Translation Steps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .290Specifying Ledgers for Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .290Specifying Rules for Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .291Specifying Output and Journal Options for Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .292Specifying Gain and Loss ChartFields for Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .293

Preparing for the Translate Within Ledger Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294Pages Used for the Translate Within Ledger Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .295Specifying a Ledger and TimeSpan for Translation Within Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .295Specifying ChartFields for Translation Within Ledger. . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .. . . . . . .296Specifying Output and Journal Options for Translation Within Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .297Specifying Gain and Loss ChartFields for Translation Within Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .297

Combining Steps Into a MultiCurrency Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298Page Used to Combine Steps in a MultiCurrency Group... . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .. . . . . . .298Combining Steps In a MultiCurrency Group.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .298

Initiating MultiCurrency Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299Page Used to Initiate MultiCurrency Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .299Requesting MultiCurrency Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .300

Putting It All Together. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Using MultiCurrency Processing in a MultiBook Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .301Comparing MultiBook Translation Ledger Results to Translation in a Single Book Environment.. . . . . . .304

Producing Revaluation and Translation Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Pages Used to Produce Revaluation and Translation Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .306

Chapter 16Performing Financial Consolidations.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309Understanding Consolidations. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309

Organizational Structure and Consolidations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .310Elimination of Intercompany Transactions... . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . .. . . . . . .311Elimination of Intercompany Investments and Calculating Minority Interests. . . . . . . . . . . . . . . . . . . . . .. . . . . . .313Components of the Consolidation Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .314

Common Elements Used in This Chapter. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Determining Consolidation ChartFields. . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .315

xii PeopleSoft Proprietary and Confidential

Contents

Consolidating on Business Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .315Consolidating on a ChartField Other Than Business Unit. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .316

Selecting an Approach to Inter/Intra Company Transactions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Defining Consolidation Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317

Defining Consolidation Scopes With Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .317Adding Detail Values.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .318

Setting Up Elimination Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319Adding an Elimination Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .319Assigning Ledgers to Elimination Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .320

Specifying Consolidation Ledgers. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .320Page Used to Define Ledger Sets. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .321Defining a Ledger Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .321

Defining Elimination Sets. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322Pages Used to Work with Elimination Sets. . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . .. . . . . . .323Defining an Elimination Set. . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . .. . . . . . .323Entering an Elimination Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .324Auditing Elimination Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .325

Defining Subsidiary Ownership and Minority Interest Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Pages Used to Define Subsidiary Ownership and Minority Interest Sets. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .326Defining Subsidiary Ownership. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .326Defining the Minority Interest Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .327Defining a Minority Interest Target. . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . .. . . . . . .328

Setting Up Consolidation Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Pages Used to Set Up Consolidation Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .329Specifying Consolidation Journal Options.. .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . .329Specifying Set Options.. . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .331

Using ChartField Value Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Performing Consolidation. . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . .332

Pages Used to Perform a Consolidation. . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . .. . . . . . .333Initiating Consolidation Processing... . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .333Viewing the Consolidation Process Log.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .335Using the Process Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .336

Consolidating Across Summary Ledgers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337Specifying Summary Ledger Consolidations. . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . .. . . . . . .337

Mapping Dissimilar Charts of Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Understanding a Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .339Pages Used for ChartField Mapping.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .341Defining a ChartField Mapping Set. .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .342Mapping ChartField Values.. . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . .. . . . . . .343

Using Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344

PeopleSoft Proprietary and Confidential xiii

Contents

Reviewing an Equitization Example. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .344Reviewing Components of the Equitization Process.. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .347

Defining Business Unit Trees and Elimination Units for Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Specifying Ledgers for Each Business Unit in an Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Defining Ownership Sets for Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Defining Equitization Rules. . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .349

Pages Used to Define Equitization Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .349Specifying the Equitization Source.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .349Specifying the Equitization Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .350Specifying the Subsidiary Offset. . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . .351Specifying Minority Interest. . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .. . . . . . .352

Defining an Equitization Group and Journal Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Page Used to Define an Equitization Group and Journal Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .352Creating an Equitization Group.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .353

Performing Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354Pages Used to Perform Equitization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .354Initiating Equitization Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .354Viewing the Equitization Process Log.. . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . .. . . . . . .357

Producing Consolidation and Equitization Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Pages Used to Produce Consolidation and Equitization Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .357

Using the Ledger Interface Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359Pages Used to Set Up the Ledger Interface Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .359Setting Up the Ledger Interface Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .359Publishing Ledger Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .362Loading External Ledger Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .362Reviewing the Process.. . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .. . . . . . .362

Chapter 17Managing Interim and Year-End Closing. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Understanding Interim and Year-End Closing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365

Interim Versus Year-End Closings.. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .365Single Versus Multiple Retained Earnings Account Closings.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .366Closings That Use Book Codes and Balance Sheet Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .368

Performing Interim Closing.. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Understanding Interim Closing.. . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . .369Performing Interim Closing Procedures.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .370Interpreting the Results of Interim Closing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .371

Performing Year-End Closing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Understanding Year-End Closings.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .372

xiv PeopleSoft Proprietary and Confidential

Contents

Completing a Year-End Procedures Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .372Performing Year-End Closing Procedures.. . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . .. . . . . . .373Interpreting Year-End Closing Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .374Defining the Relationship of Interim Close to Year-End Close.. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .375

Defining Closing Rules. . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . .376Understanding Closing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .376Pages Used to Define Closing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .377Selecting Closing Rules Closing Options.. . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . .. . . . . . .377Specifying Net Income and Retained Earnings ChartField Values.. . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . .. . . . . . .380Specifying Journal Options .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .383Specifying Roll-Forward Options .. . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . .. . . . . . .385

Running the Close Application Engine Process (GLPCLOSE).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386Pages Used to Run the Close Application Engine Process (GLPCLOSE). . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .386Creating the Close Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .386Monitoring Validation Checking.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .388

Processing an Undo Close.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389Undoing an Interim Close.. . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . .. . . . . . .389Undoing a Year-End Close.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .389

Producing Interim and Year-End Closing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390Pages Used to Produce Interim and Year-End Closing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .390Generating the Journal Closing Status Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .390

Chapter 18Reviewing Financial Information... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393Understanding Ledger, Journal, and Financial Information Inquiries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393

Inquiry Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .394Viewing Journal Information.. . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . . .395

Pages Used to Review Journal Information.. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .395Entering Journal Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .395Viewing Journal Header Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .396

Viewing Ledger Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397Pages Used to Review Ledger Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .398Specifying Ledger Criteria to Review Summary and Detail Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .399Viewing Ledger Summary Balances.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .401Viewing Ledger Transaction Details. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . .. . . . . . .402Viewing Detail Journal Header and Journal Lines.. . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . .. . . . . . .403Drilling Down to the Subsystem Accounting Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .404Viewing the Ledger Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .404

Inquiring About Ledger Groups .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405

PeopleSoft Proprietary and Confidential xv

Contents

Pages Used to Review Ledger Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .405Reviewing Ledger Group Information.. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .405Viewing Journal Lines.. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . .406

Configuring Ledger Summary and Detail Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Pages Used to Review Ledger Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .407Adding Summary Inquiry Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .408Adding Detail Inquiry Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .408

Comparing Data by Ledger Periods.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409Pages Used to Compare Data by Ledger Period.. . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . .. . . . . . .410Entering Search Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .410Comparing a Ledger by Period.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .412

Comparing Across Ledgers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413Pages Used to Compare Ledgers Across Periods.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .414Entering Comparison Criteria for Two Ledgers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .414Reviewing Comparison Amounts Between The Ledgers by Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .415Using a Chart to Analyze the Ledger Comparison Data. . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . .416

Reviewing Imported Accounting Entries. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .417Pages Used to Inquire on Accounting Lines.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .418Inquiring on Imported Accounting Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .418

Reviewing Entry Event Accounting. . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . . . . . .419Pages Used to Review Entry Event Accounting. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .419Drilling Down to Entry Event Budget Accounting Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .419Drilling Down to the Entry Event GL Adjustment Accounting Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .420

Chapter 19Maintaining Standard Budgets in PeopleSoft General Ledger.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421Understanding PeopleSoft General Ledger Standard Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .421Methods for Creating and Maintaining Standard Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .422Budget Spreading, Repeating, and Percentage-Increase Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .423Budget Copy Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .425Budget Allocation Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .425

Maintaining Detail Budgets. . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .426Pages Used to Maintain Detail Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .427Selecting Budget ChartField Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .427Adjusting Budget Data by Year. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .428Adjusting Budget Data by Period.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .429Using the Budget Calculator Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .430

Maintaining Project Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431

xvi PeopleSoft Proprietary and Confidential

Contents

Pages Used to Maintain Project Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .432Reviewing and Modifying Project Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .432

Copying Budgets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432Pages Used to Copy Budgets. . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . .. . . . . . .433Setting Up the Budget Copy Definition Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .433Setting Up the Budget Copy Definition Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .435Creating a Budget Copy Group .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .436Initiating Budget Copy Processing .. .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .437

Importing Budgets from Spreadsheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437Posting Budget Journals.. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . .438

Chapter 20Archiving Ledgers and Journals... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .439Understanding Archiving.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .439

Archival to a Table or File. .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .439Retention Days and Archive Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .440

Archiving and Restoring Ledgers. .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .441Pages Used to Archive and Restore Ledgers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .442Archiving a Ledger. . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . .. . . . . . .442Restoring Archived Ledger Data. . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . .. . . . . . .443Viewing the Archive Ledger Log.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .444

Archiving and Restoring Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445Pages Used to Archive and Restore Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .445Archiving Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .445Restoring Archived Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .446Viewing the Archive Journals Log.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .446

Chapter 21Using Commitment Control in PeopleSoft General Ledger.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .449Understanding Commitment Control and General Ledger Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .449

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .449Commitment Control Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .450

Entering and Processing Commitment Control Journal Entries in General Ledger. . . . . . . . .. . . . . . . . . . . . . . . . . .451Pages Used to Enter and Process Commitment Control Journal Entries in General Ledger. . . .. . . . . . .452Entering Header Information for Commitment Control Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .453Using Commitment Control Amount Types.. . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . .. . . . . . .454Entering and Processing Commitment Control Journal Lines.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .457

Enter and Process Commitment Control Journal Entries with Entry Events in General Ledger. . . . . . . . . . . .458

PeopleSoft Proprietary and Confidential xvii

Contents

Reviewing and Correcting Journal Entries with Budget Checking Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .458Pages Used to Review and Correct Commitment Control Journal Errors. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .459Reviewing and Interpreting Commitment Control Journal Status Codes.. . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . .460Overriding Journal Entry Budget Checking Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .460Viewing Journal Header with Budget Exceptions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .460Viewing Journal Lines with Budget Exceptions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .462

Chapter 22Approving Journal Entry.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465Understanding the Journal Entry Approval Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465

Business Process Maps and PeopleSoft Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .465Journal Entry Approvals Using PeopleSoft Workflow.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .465Journal Entry Approvals Using PeopleSoft System Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .468

Setting Up Journal Entry Approval in PeopleSoft Workflow.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .468Pages Used to Set Up Journal Entry Approval in PeopleSoft Workflow.. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .470Reviewing the Current Workflow Approval Setup.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .470Modifying the Workflow Approval Rule Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .471Modifying the Rule Set Definition Properties for a Workflow Item.. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . .472Defining the Rules for a Journal Entry Approval Workflow Item.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .473Setting Up the Events for a Journal Entry Approval Workflow Item.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .474

Chapter 23Using Entry Events in PeopleSoft General Ledger... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .477Understanding Entry Events in PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .477

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .477PeopleSoft General Ledger Entry Event Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .478Entry Event Source Definitions, Processes, Steps, and Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .479GLJE Entry Event Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .480GLJEADJ Entry Event Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .480Multibook Ledgers Using Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .481Interunit Journal Entries Using Entry Events. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . .481Allocations Using Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .483Standard Journal Entries Using Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .483Separate Debit and Credit Journal Entries Using Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .483Flat File Journal Imports Using Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .484Spreadsheet Journal Imports Using Entry Events. .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . .484Copy Entry Event Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .484Entry Event Journal Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .484

xviii PeopleSoft Proprietary and Confidential

Contents

Creating and Processing Journal Entries with Entry Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .484Pages Used to Create and Process Journal Entries with Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .485Creating and Processing Entry Event Journals Using GLJE Entry Event Process. . . . . . . . . . . . . . . .. . . . . . .486Creating Budget Adjustment Journal Entries Using the GLJEADJ Entry Event Process. . . . . . . . .. . . . . . .487

Correcting Entry Event Journal Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .488Correcting Journal Entry Errors Containing Entry Events with Suspense Option Off. . . . . . . . . . . . .. . . . . . .488Correcting Journal Entry Errors Containing Entry Events with Suspense Option On. . . . . . . . . . . . .. . . . . . .489Drilling Down to Entry Event Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .489

Chapter 24Using OLAP Tools to Analyze General Ledger Data .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491Understanding OLAP Cubes.. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .491Planning the OLAP Database.. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .492Preparing Trees and Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .492Defining the Cube.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .493Building the Cube.. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .494

Understanding Cube Building.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .494Page Used to Build a General Ledger Cube.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .494Building a Ledger Cube.. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .494

Analyzing Cube Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496

Chapter 25Federal Government, Statutory, and XBRL Financial Statement Reporting... . . . . . . . . . . . . . . . . .497Understanding Federal Government, Statutory, and XBRL Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .497

PeopleSoft Federal Government Reporting. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .497PeopleSoft Statutory Reporting. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .500PeopleSoft XBRL Financial Statement Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .500

Setting Up FACTS I Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .500Understanding FACTS I Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .501Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .503Pages Used to Set Up FACTS I Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .504Setting Up FACTS I ChartField Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .504Specifying Miscellaneous ChartFields for FACTS I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .505

Setting Up FACTS I Trees.. . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .506Pages Used to Set Up FACTS I Trees.. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . .507Setting Up a FACTS I (FACTS II) Transfer Agency Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .507Setting Up a FACTS I Bureau Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .508Setting Up a FACTS I Fund Group Tree.. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .509

PeopleSoft Proprietary and Confidential xix

Contents

Setting Up a FACTS I Department Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .510Setting Up a FACTS I Account Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .511Setting Up a FACTS I Exchange/ Acct Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .512Setting Up a FACTS I Custodial/ Acct Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .513Setting Up a FACTS I Budget Subfunction/ Acct Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .514Setting Up a FACTS I/II Transaction Partner Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .515Setting Up a FACTS I Transaction Partner/ AcctTree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .516Setting Up a FACTS I Accounts Requiring Attributes Tree.. .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . .517Creating a Tree Group for FACTS I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .518Configuring TableSet Control for FACTS I Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .520Configuring TableSet Control Records Groups for FACTS I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .520Configuring TableSet Control Trees for FACTS I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .522

Setting Up and Generating a FACTS I Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522Page Used to Generate a FACTS I Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .523Loading MAF and FACTS I Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .523Reviewing FACTS I MAF Data.. . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . .524Setting Up and Generating a FACTS I Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .525

Setting Up FACTS II Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .526Understanding FACTS II Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .527Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .528Pages Used to Set Up FACTS II Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .529Entering FACTS II Contact Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .531Creating the Preparer File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .532Setting Up ChartField Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .533Linking Attributes ChartFields. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . .542Selecting ChartField Attributes. . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . .543Linking Account Attributes and Values to Account ChartFields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .544Specifying Miscellaneous ChartFields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .544Setting Up Attribute Cross-References.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .545Selecting Attribute Cross References for FACTS II Accounting Edits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .545Loading MAF Data.. . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . .. . . . . . .546Reviewing the MAF File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .547Setting Up the FACTS II Treasury Symbol Cross-References.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .549

Creating FACTS II Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .549Pages Used to Create FACTS II Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .550Using Trees to Control Roll-up of ChartField Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .551Creating a FACTS II Account Roll-up Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .552Creating a Cohort Year Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .553Creating a Category B Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .553Creating the Accounts Requiring Fund Attributes Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .554

xx PeopleSoft Proprietary and Confidential

Contents

Creating the Transfer Agency Tree.. . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . .. . . . . . .556Creating the Transfer Account Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .557Creating the Transaction Partner Tree... . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .558Creating a Tree Group for FACTS II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .560Configuring TableSet Control for FACTS II Processing.. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .560Configuring the TableSet Control Record Group Page.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .561Configuring the TableSet Control Tree Page.. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . .. . . . . . .562

Generating a FACTS II Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .562Pages Used to Generate a FACTS II Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .563Reviewing FACTS II Data Setup.. . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . .. . . . . . .564Accumulating the FACTS II Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .565Reviewing the FACTS II Header Information.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .566Reviewing the FACTS II Detail Balances.. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . .566Reviewing the FACTS II Detail Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .567Reviewing and Modifying FACTS II Footnotes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .568Validating the FACTS II Data. . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . .. . . . . . .569Creating the FACTS II File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .569Running the Ledger With Attributes Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .570

Creating SF224, SF1219, and SF1220 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571Understanding SF224/1220 and SF1219 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .571Pages Used to Define and Generate the SF224/1220 and SF1219 Reports. . . . . . . . . . . . . . . . . . . . . . .. . . . . . .572Defining the SF224/1220 Report Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .572Defining the SF224/1220 Entry Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .573Defining SF224/1220 Undeposited Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .574Generating SF224/1220 Report Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .575Printing the SF224 Report and Creating the Flat File. . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . .. . . . . . .577Defining the SF1219 Report. . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . .. . .. . . . . . .577Printing the SF1219 Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .577Printing the SF1220 Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .578Creating the SF1219/1220 Flat File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .578

Defining and Generating a Fund Balance Reconciliation Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578Understanding Fund Balance Reconciliation Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .578Pages Used to Define and Generate the Fund Balance Reconciliation Report. . . . . . . . . . . . . . . . . . . .. . . . . . .579Defining the General Ledger Accounts to Reconcile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .579Defining Entry Events to Reconcile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .580Importing the U.S. Treasury Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .580Generating the Fund Balance Reconciliation Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .581

Configuring the FUND_STATUS PS/nVision Report. .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .581Pages Used to Configure the FUND_STATUS PS/nVision Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .582Maintaining the FED_RC02_Accounts Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .582

PeopleSoft Proprietary and Confidential xxi

Contents

Defining the FUND_BALANCE nVision Report Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .583Requesting and Distributing the FUND_BALANCE Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .584

Setting Up Federal Reimbursable Agreement Accounts in General Ledger. . . .. . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .586Understanding Federal Reimbursable Accounts in General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .586Pages Used to Set Up Reimbursable Agreement Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .587Setting Up Reimbursable Agreement Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .587

Using PSnVision for Statutory Reporting. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588Understanding GASB 34/35 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .588

Using XBRL to Produce Balance Sheets and Income Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588Understanding XBRL Financial Statements. . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . .. . . . . . .589Pages Used to Produce Financial Statements Using XBRL.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .590Setting Up Supporting Trees and ChartField Value Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .590Specifying the XBRL Context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .590Specifying a NameSpace Alias for the NameSpace URL.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .591Defining the XBRL Elements. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . .591Setting Up the XBRL Instance Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .592Defining the Report Elements for the Instance Template. . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .. . . . . . .593Running XBRL Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .594

Appendix AConfiguring Batch Processes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .597Configuring Temporary Tables for Batch Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .597

Appendix BDelivered Workflows for PeopleSoft General Ledger... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599Delivered Workflows for PeopleSoft General Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .599

Journal Entry Approval. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . .599Journal Entry Denial. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . . . .599Journal Entry Approval. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . .600

Appendix CPeopleSoft General Ledger Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .601PeopleSoft General Ledger Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .601

xxii PeopleSoft Proprietary and Confidential

Contents

Glossary of PeopleSoft Terms... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615

Index .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .631

PeopleSoft Proprietary and Confidential xxiii

Contents

xxiv PeopleSoft Proprietary and Confidential

About These PeopleBooks

PeopleBooks provide you with the information that you need to implement and use PeopleSoft applications.

This preface discusses:

• PeopleSoft application prerequisites.

• PeopleSoft application fundamentals.

• Related documentation.

• Typographical elements and visual cues.

• Comments and suggestions.

• Common elements in PeopleBooks.

Note. PeopleBooks document only page elements that require additional explanation. If a page elementis not documented with the process or task in which it is used, then either it requires no additionalexplanation or it is documented with common elements for the section, chapter, PeopleBook, or productline. Elements that are common to all PeopleSoft applications are defined in this preface.

PeopleSoft Application PrerequisitesTo benefit fully from the information that is covered in these books, you should have a basicunderstanding of how to use PeopleSoft applications.

SeeUsing PeopleSoft Applications.

You might also want to complete at least one PeopleSoft introductory training course.

You should be familiar with navigating the system and adding, updating, and deleting information byusing PeopleSoft windows, menus, and pages. You should also be comfortable using the World WideWeb and the Microsoft Windows or Windows NT graphical user interface.

These books do not review navigation and other basics. They present the information that you needto use the system and implement your PeopleSoft applications most effectively.

PeopleSoft Application FundamentalsEach application PeopleBook provides implementation and processing information for your PeopleSoftdatabase. However, additional, essential information describing the setup and design of your systemappears in a companion volume of documentation called the application fundamentals PeopleBook.Each PeopleSoft product line has its own version of this documentation.

PeopleSoft Proprietary and Confidential xxv

General Preface

The application fundamentals PeopleBook consists of important topics that apply to many or allPeopleSoft applications across a product line. Whether you are implementing a single application,some combination of applications within the product line, or the entire product line, you shouldbe familiar with the contents of this central PeopleBook. It is the starting point for fundamentals,such as setting up control tables and administering security.

Related DocumentationThis section discusses how to:

• Obtain documentation updates.

• Order printed documentation.

Obtaining Documentation UpdatesYou can find updates and additional documentation for this release, as well as previous releases,on the PeopleSoft Customer Connection web site. Through the Documentation section ofPeopleSoft Customer Connection, you can download files to add to your PeopleBook Library.You’ll find a variety of useful and timely materials, including updates to the full PeopleSoftdocumentation that is delivered on your PeopleBooks CD-ROM.

Important! Before you upgrade, you must check PeopleSoft Customer Connection for updates to theupgrade instructions. PeopleSoft continually posts updates as the upgrade process is refined.

See Also

PeopleSoft Customer Connection web site, http://www.peoplesoft.com/corp/en/login.asp

Ordering Printed DocumentationYou can order printed, bound volumes of the complete PeopleSoft documentation that is deliveredon your PeopleBooks CD-ROM. PeopleSoft makes printed documentation available for eachmajor release shortly after the software is shipped. Customers and partners can order printedPeopleSoft documentation by using any of these methods:

• Web

• Telephone

• Email

Web

From the Documentation section of the PeopleSoft Customer Connection web site, access the PeopleSoftPress web site under the Ordering PeopleBooks topic. The PeopleSoft Press web site is a joint venturebetween PeopleSoft and Consolidated Publications Incorporated (CPI), the book print vendor. Use acredit card, money order, cashier’s check, or purchase order to place your order.

xxvi PeopleSoft Proprietary and Confidential

General Preface

Telephone

Contact CPI at 800 888 3559.

Email

Send email to CPI at [email protected].

See Also


Typographical Conventions and Visual CuesThis section discusses:

• Typographical conventions.

• Visual cues.

Typographical ConventionsThe following table contains the typographical conventions that are used in PeopleBooks:

Typographical Convention or Visual Cue Description

Bold Indicates PeopleCode function names, method names,language constructs, and PeopleCode reserved words thatmust be included literally in the function call.

Italics Indicates field values, emphasis, and PeopleSoft or otherbook-length publication titles. In PeopleCode syntax,italic items are placeholders for arguments that yourprogram must supply.

We also use italics when we refer to words as words orletters as letters, as in the following: Enter the number 0,not the letterO.

KEY+KEY Indicates a key combination action. For example, a plussign (+) between keys means that you must hold downthe first key while you press the second key. For ALT+W,hold down the ALT key while you press W.

Monospace font Indicates a PeopleCode program or other code example.

“ ” (quotation marks) Indicate chapter titles in cross-references and words thatare used differently from their intended meanings.

PeopleSoft Proprietary and Confidential xxvii

General Preface

Typographical Convention or Visual Cue Description

. . . (ellipses) Indicate that the preceding item or series can be repeatedany number of times in PeopleCode syntax.

{ } (curly braces) Indicate a choice between two options in PeopleCodesyntax. Options are separated by a pipe ( | ).

[ ] (square brackets) Indicate optional items in PeopleCode syntax.

& (ampersand) When placed before a parameter in PeopleCode syntax,an ampersand indicates that the parameter is an alreadyinstantiated object.

Ampersands also precede all PeopleCode variables.

(ISO) Information that applies to a specific country, to the U.S.federal government, or to the education and governmentmarket, is preceded by a three-letter code in parentheses.

The code for the U.S. federal government is USF;the code for education and government is E&G, andthe country codes from the International StandardsOrganization are used for specific countries. Here is anexample:

(GER) If you’re administering German employees,German law requires you to indicate special nationalityand citizenship information for German workers usingnationality codes established by the German DEUEVDirective.

Cross-references PeopleBooks provide cross-references either belowthe heading “See Also” or on a separate line precededby the wordSee.Cross-references lead to otherdocumentation that is pertinent to the immediatelypreceding documentation.

Visual CuesPeopleBooks contain the following visual cues.

Notes

Notes indicate information that you should pay particular attention to as you work with the PeopleSoft system.

Note. Example of a note.

A note that is preceded byImportant! is crucial and includes information that concernswhat you must do for the system to function properly.

xxviii PeopleSoft Proprietary and Confidential

General Preface

Important! Example of an important note.

Warnings

Warnings indicate crucial configuration considerations. Pay close attention to warning messages.

Warning! Example of a warning.

Comments and SuggestionsYour comments are important to us. We encourage you to tell us what you like, or whatyou would like to see changed about PeopleBooks and other PeopleSoft reference andtraining materials. Please send your suggestions to:

PeopleSoft Product Documentation Manager PeopleSoft, Inc. 4460 Hacienda Drive Pleasanton, CA 94588

Or send email comments to [email protected].

While we cannot guarantee to answer every email message, we will pay careful attentionto your comments and suggestions.

Common Elements in These PeopleBooksAs of Date The last date for which a report or process includes data.

Business Unit An ID that represents a high-level organization of business information.You can use a business unit to define regional or departmentalunits within a larger organization.

Description Enter up to 30 characters of text.

Effective Date The date on which a table row becomes effective; the date that an actionbegins. For example, to close out a ledger on June 30, the effective datefor the ledger closing would be July 1. This date also determines whenyou can view and change the information. Pages or panels and batchprocesses that use the information use the current row.

Once, Always,andDon’tRun

Select Once to run the request the next time the batch process runs. After thebatch process runs, the process frequency is automatically set to Don’t Run.

Select Always to run the request every time the batch process runs.

Select Don’t Run to ignore the request when the batch process runs.

Report Manager Click to access the Report List page, where you can view report content,check the status of a report, and see content detail messages (which showyou a description of the report and the distribution list).

PeopleSoft Proprietary and Confidential xxix

General Preface

Process Monitor Click to access the Process List page, where you can view thestatus of submitted process requests.

Run Click to access the Process Scheduler request page, where you can specify thelocation where a process or job runs and the process output format.

Request ID An ID that represents a set of selection criteria for a report or process.

User ID An ID that represents the person who generates a transaction.

SetID An ID that represents a set of control table information, or TableSets.TableSets enable you to share control table information and processing optionsamong business units. The goal is to minimize redundant data and systemmaintenance tasks. When you assign a setID to a record group in a businessunit, you indicate that all of the tables in the record group are shared betweenthat business unit and any other business unit that also assigns that setID tothat record group. For example, you can define a group of common job codesthat are shared between several business units. Each business unit that sharesthe job codes is assigned the same setID for that record group.

Short Description Enter up to 15 characters of text.

See Also

Using PeopleSoft Applications

PeopleSoft Process Scheduler

xxx PeopleSoft Proprietary and Confidential

PeopleSoft General Ledger Preface


• PeopleSoft application fundamentals

• Deferred Processing

• Common elements in this PeopleBook.

Note. This PeopleBook documents only page elements that require additional explanation. If a pageelement is not documented with the process or task in which it is used, then it either requires no additionalexplanation or is documented with the common elements for the section, chapter, or PeopleBook.

PeopleSoft Application FundamentalsThe PeopleSoft General Ledger PeopleBookprovides you with implementation and processinginformation for your PeopleSoft General Ledger system. However, additional, essential informationdescribing the setup and design of your system resides in companion documentation. The companiondocumentation consists of important topics that apply to many or all PeopleSoft applicationsacross the Financials, Enterprise Service Automation, and Supply Chain Management productlines. You should be familiar with the contents of these PeopleBooks.

The following companion PeopleBooks apply specifically to PeopleSoft to PeopleSoft General Ledger.

• PeopleSoft Application Fundamentals for FIN, ESA, and SCM PeopleBook

• Setting Up Global Options and Reports

• Setting Up and Using Commitment Control

• Working With Third-Party Applications

Deferred ProcessingSeveral pages in the PeopleSoft General Ledger applications operate in deferred processing mode.Most fields on these pages are not updated or validated until you save the page or refresh it byclicking a button, link, or tab. This delayed processing has various implications for the field valueson the page. For example, if a field contains a default value, any value that you enter before thesystem updates the page overrides the default. Another implication is that the system updates quantitybalances or totals only when you save or otherwise refresh the page.”

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions,Enterprise Service Automation, and Supply Chain Management PeopleBook, “PeopleSoftApplication Fundamentals PeopleBook Preface”.

PeopleSoft Proprietary and Confidential xxxi

Preface

Common Elements Used in This PeopleBookAccount ChartField that identifies the nature of a transaction for corporate accounts.

Accounting Date Date for accounting entries for an activity.

Affiliate ChartField used to map transactions between business units whenusing a single interunit account.

Alt Acct (alternate account) ChartField that identifies the nature of a transaction for statutory accounts.This field appears only if you enable the Alternate Account option foryour organization and for the general ledger business unit.

As of Date The last date for which a report or process includes data.

Balance Amount of an item that is still open (unpaid).

Budget Ref (budgetreference)

ChartField that identifies unique control budgets when individual budgetsshare budget keys and overlapping budget periods.

Business Unit An identification code that represents a high-level organization ofbusiness information. You can use a business unit to define regional ordepartmental units within a larger organization.

Chartfield 1 to Chartfield 3 ChartFields that you configure to meet your organization’s requirements.

Class ChartField that identifies a particular appropriation when you combine itwith a Fund, DeptID, Program Code, and Budget Reference.

Group of customers in a trade, such as grocers or mass merchandisers.

Currency Code that identifies the type of currency for an amount, such as USD or FRF.

Dept (department) ChartField that indicates who is responsible for or affected by the transaction.

Description Freeflow text up to 30 characters

Division Geographic area within an organization.

Document SequenceorDocument Sequencing

Click to open a page where you can enter document sequencing information.This option is available only if you enable the document sequencingfeature for the PeopleSoft General Ledger business unit.

Effective Date Date on which a table row becomes effective; the date that an actionbegins. For example, the General Ledger Account page contains EffectiveDate and is used in conjunction with Status to determine on whichdate the Account is activated or inactivated. This date also determineswhen you can view and change information. Pages or panels and batchprocesses that use the information use the current row.

Entry Event Code that identifies the entry event definition that is used to createsupplemental accounting entries for the transaction. You define thesecodes on the Entry Event Code Def’n page.

xxxii PeopleSoft Proprietary and Confidential

Preface

Entry Reason The reason that is associated with an item that defines which accountingentries to generate and can be used for reporting purposes.

Entry Type ID that identifies the type of activity, such as invoice or pay an item.

Exchange Rate Rate that is used for currency conversion.

Fund ChartField that represents structural units for education and governmentaccounting. Can also represent a divisional breakdown in your organization.

Fund Affiliate ChartField that is used to correlate transactions between fundswhen using a singe intraunit account.

Journal Created when you edit journal lines (accounting entries) online inPeopleSoft General Ledger or you run the Journal Generator processfor subsystem, imported, or batch accounting entries.

Journal Entry Enter a journal line consisting of accounting and ChartField informationin PeopleSoft General Ledger Create Journal Entries.

Journal Header The first page entered to create journal entries in PeopleSoft GeneralLedger which includes the overall journal information such as the ledger,the journal source, long and short descriptions and more.

Journal Line Refers to each accounting line entered in PeopleSoft General Ledger CreateJournal Entries consisting of appropriate ChartField and accounting values.

Language or LanguageCode

The language in which you want the field labels and report headings of yourreports to print. The field values appear as you enter them. Language alsorefers to the language spoken by an employee, applicant, or non-employee.

Oper Unit (operating unit) ChartField that is used to identify a location, such as a distributionwarehouse or sales center.

Operating Unit Affiliate ChartField that is used to correlate transactions between operatingunits when using a singe intraunit account.

Process Frequencyor When Designates the appropriate frequency in the Process Frequency group box:

Once:Executes the request the next time that the batch process runs. After thebatch process runs, the process frequency is automatically set toDon’t Run.

Always: Executes the request every time that the batch process runs.

Don’t Run: Ignores the request when the batch process runs.

Process Monitor This link takes you to the Process List page, where you can viewthe status of submitted process requests.

Product ChartField that captures additional information that is useful for profitabilityand cash flow analysis by product sold or manufactured.

Program ChartField that identifies groups of related activities, cost centers,revenue centers, responsibility centers, and academic programs. Tracksrevenue and expenditures for programs.

Project ChartField that captures information for project or grants accounting.

PeopleSoft Proprietary and Confidential xxxiii

Preface

Project ID Project ID that is assigned to a project that is related to the item. Theproject must already be established in PeopleSoft Project.

Report ID Identifies the report being processed and generated.

Report Manager This button takes you to the Report List page, where you can view reportcontent, check the status of a report, and see content detail messagesthat describe the report and the distribution list.

Process Monitor This button takes you to the Process List page, where you can viewthe status of submitted process requests.

Report ID The report identifier.

Report Manager This link takes you to the Report List page, where you can view reportcontent, check the status of a report, and see content detail messages (whichshow you a description of the report and the distribution list).

Run This button takes you to the Process Scheduler Request page, where you canspecify the location where a process or job runs and the process output format.

Run Control ID A request identification that represents a set of selection criteriafor a report or process.

Request ID A request identification that represents a set of selection criteriafor a report or process.

SetID An identification code that represents a set of control table information orTableSets. A TableSet is a group of tables (records) necessary to defineyour company’s structure and processing options.

Short Description User defined text up to 15 characters.

User ID The system identifier for the individual who generates a transaction.

See Also

PeopleSoft PeopleTools PeopleBook: Process Scheduler, "Understanding PeopleSoft Process Scheduler"

PeopleSoft PeopleTools PeopleBook: Using PeopleSoft Applications, "Working withPages," Using Effective Dates

xxxiv PeopleSoft Proprietary and Confidential

CHAPTER 1

Getting Started With PeopleSoft General Ledger

This chapter provides an overview of PeopleSoft General Ledger and introduces:

• PeopleSoft General Ledger business processes.

• PeopleSoft General Ledger integrations touchpoints.

• PeopleSoft General Ledger implementation tasks.

PeopleSoft General Ledger Business ProcessesWe cover these business processes in the business process chapters of this General Ledger PeopleBook:

• Create and process journal entries.

• Build summary ledgers.

• Close ledgers.

• Process multiple currency

• Create and process Average Daily Balance (ADB).

• Create and process open items.

• Consolidate financial data.

• Maintain standard budgets

• Monitor background processes.

• Review financial information.

• Archive tables.

• Generate regulatory ledger reports

• Create XBRL documents.

• Generate general reports.

• Generate federal reports.

• Create and process allocations.

• Generate statutory reports.

• Create and process interunit and intraunit transactions.

• Create and process Commitment Control transactions in General Ledger.

PeopleSoft Proprietary and Confidential 1

Getting Started With PeopleSoft General Ledger Chapter 1

• Create and process entry event transactions.

• Process subsystem journals using Journal Generator.

• Import and process spreadsheet journal entries.

• Import and process transactions from a flat file.

• Enter and process statistical transactions.

• Enter and process Value Added Tax (VAT) transactions.

• Approving journal entries for processing.

• Running General Ledger background processes.

PeopleSoft General Ledger IntegrationsPeopleSoft General Ledger serves as the core of the PeopleSoft Financial Management System. ThePeopleSoft subsystem applications, such as Payables and Receivables, create accounting entries that you selectto process in the journal generator. Journal generator creates the appropriate journals from the accountingentries and sends them to General Ledger for posting to the appropriate ledgers. From this posted accountingdata, you can obtain both detail and summary accounting information and produce numerous financial reportsfor your organization. There are four major ways of integrating data into General Ledger:

• Database tables — PeopleSoft subsystem applications running in the same database create accountingentries in a table. You run Journal Generator to create journals from these accounting tables.

• Application messaging — PeopleSoft subsystem applications from a different database create accountingentries and use application messaging to send them to General Ledger. You run Journal Generator to createjournals and optionally send the updated journal information back to the subsystem using applicationmessaging. Remote subsystems also use application messaging to perform various validation and datasynchronization activities and to send commitment control budget journals to PeopleSoft General Ledger.

• Flat File Imports — PeopleSoft General Ledger has several file import processes for you to importjournals, ledger data, and commitment control budgets into the system.

• XML import over internet — PeopleSoft General Ledger delivers a Spreadsheet Journal interface for you toprepare your journals offline and then import them over the internet using XML and HTTP connection. TheExcel to Component Interface utility uses the same mechanism to import data into various setup tables.

This diagram details all types of integration with PeopleSoft General Ledger:

2 PeopleSoft Proprietary and Confidential

Chapter 1 Getting Started With PeopleSoft General Ledger

PeopleSoft GLSpreadsheet

JournalExternalSystem

SpreadsheetJournal Import

Flat FileJournal Import

Journals

JournalGenerator

Posting

AccountingTables

StandardDetail

Ledger

Genericaccounting

entry

HCM, LS, ELMaccounting

entry

A

StandardBudgetLedger

LEDGER_BUDG_KK

CommitmentControl

Journals

CommitmentControl BudgetJournal Import

AllocationCommitment

Control Posting

CommitmentControl LedgerSummary

Ledger

Ledger Load(ChartField

value mapping)LedgerPublish

Flat FileLedger Import

PeopleSoft GL(regional)

ExternalSystem

ExternalSystem

Commitment ControlBudget Update

Ledgerinterface

PeopleSoftGeneral Ledger

ExternalSystem

North America Payroll,Global Payroll,

Learning Solutions,Enterprise Learning

Management

HCM North America Payroll

EPM Budgeting

ETLUtility

A

ChartField

BusinessUnit

LedgerDefinition

XBRLDocument

SpeedType

JournalGeneratorTemplate

ComboData Table

Calendar

Combo EditRequest/

Reply

Budget CheckTransaction

BudgetProcessor

ExternalSystem

General Ledger Integration Map

We discuss integration in both the implementation and processing sections of thePeopleSoft General Ledger PeopleBook.

Supplemental information about third-party application integrations is located on thePeopleSoft Customer Connection website.



See Also

Chapter 6, “ Integrating and Transferring Information Among Applications ,” page 63

PeopleSoft General Ledger ImplementationPeopleSoft Setup Manager enables you to review a list of setup tasks for your organization for the products thatyou are implementing. The setup tasks include the components that you must set up, listed in the order in whichyou must enter data into the component tables, and links to the corresponding PeopleBook documentation.

PeopleSoft General Ledger also provides component interfaces to help you load and initialize setupdata from you existing system into PeopleSoft General Ledger tables. Use the Excel to ComponentInterface utility with the component interfaces to populate the tables.

This table lists all components that have a component interface delivered for use withthe Excel to Component Interface import utility.

Note. The Excell to Component Interface import utility is delivered for a technical userto use for data conversion during implementation.

Component Component Interface References

ALTACCT

Alternate Account ChartField

ALTACCT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Alternate Account Values..

BD_SCENARIO

Budget Scenario ChartField

BUDGET_SCENARIO SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Scenario Values.

BUDREF_PNL

Budget Reference ChartField

BUDGET_REF_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Budget Reference Values.




CHARTFIELD1

ChartField1

CHARTFIELD1 SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Values for ExpansionChartFields 1, 2, and 3.

CHARTFIELD2

ChartField2


CHARTFIELD3

ChartField3


CLASS_PNL

Class ChartField

CLASS_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Class Field Values.

DEPARTMENT

Department ChartField

DEPT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Department Values.

FUND_DEFINITION

Fund ChartField

FUND_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Fund Code Values.




GL_ACCOUNT

Account ChartField

ACCOUNT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Account Values.

GL_PE_CF_SEC_COMP

ChartField pagelet security

SECURITY_CF_PAGELET SeePeopleSoft Financials PortalPack 8.8 and Enterprise ServiceAutomation Portal Pack 8.8PeopleBook, “Using PeopleSoftFinancials Portal Pack”.

IU_INTER_PR_BASIC

Inter Unit pair mass manienance

IU_PAIRS_MAINT SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Using Interunit and IntraunitAccounting and ChartFieldInheritance,” Setting Up Interunitand Intraunit Processing.

IU_INTER_TMPLT

Inter Unit template

IU_INTER_TMPLT SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Using Interunit and IntraunitAccounting and ChartFieldInheritance,” Defining InterunitTemplates.

IU_INTRA_TMPLT

Intra Unit template

IU_INTRA_TMPLT SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Using Interunit and IntraunitAccounting and ChartFieldInheritance,” Defining IntraunitTemplates.

LEDGER_SECURITY

nVision Ledger Security

SECURITY_NVISION_LEDGER SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Securing Your System,” DefiningRow-Level Security.




OPERATING_UNIT

Operating Unit ChartField

OPER_UNIT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Operating Unit Values.

OPR_DEFAULT_FIN

User Preferences

OPR_DEFAULT_FIN SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining User Preferences,”Defining Cross-Application UserPreferences.

PRODUCT

Product ChartField

PRODUCT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Product Values.

PROGRAM_DEFINITION

Program ChartField

PROGRAM_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Program Code Values.

PROJECT

Project ChartField

PROJECT_CF SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Project Values.

SEC_BU_CLS

Business Unit Security byPermission List

SECURITY_BU_CLS SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Securing Your System,” DefiningRow-Level Security.




SEC_BU_OPR

Business Unit Security by User ID

SECURITY_BU_OPR SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Securing Your System,” DefiningRow-Level Security.

SEC_LEDGER_CLS

Ledger Security by PermissionList

SECURITY_LEDGER_CLS SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Securing Your System,” DefiningRow-Level Security.

SEC_LEDGER_OPR

Ledger Security by User ID

SECURITY_LEDGER_OPR SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Securing Your System,” DefiningRow-Level Security.

STATISTICS_TBL

Statistics Code

STATISTICS_CODE SeePeopleSoft 8.8 ApplicationFundamentals for FinancialManagement Solutions, EnterpriseService Automation, and SupplyChain Management PeopleBook,“Defining and Using ChartFields,”Adding Statistics Code Values.

TAX_AUTHORITY_VAT

Value Added Tax Authority

TAX_AUTHORITY_VAT SeePeopleSoft Global Optionsand Reports 8.8 PeopleBook,“Working with Value Added Taxes(VAT),” Defining VAT Authorities.

TAX_BU_CODE_VAT

VAT Accounts by Business Unitcomponent

TAX_BU_CODE_VAT SeePeopleSoft Global Optionsand Reports 8.8 PeopleBook,“Working with Value Added Taxes(VAT),” Defining VAT Accountsby General Ledger Business Unit(Optional).




TAX_CODE_VAT

Value Added Tax Code

TAX_CODE_VAT SeePeopleSoft Global Optionsand Reports 8.8 PeopleBook,“Working with Value Added Taxes(VAT),” Defining VAT CodesUsing the Value Added Tax CodePage.

VAT_ENTITY_ID

Value Added Tax Entity

VAT_ENTITY_ID SeePeopleSoft Global Optionsand Reports 8.8 PeopleBook,“Working with Value Added Taxes(VAT),” Entering VAT EntityIdentification Information.

Other Sources of Information

In the planning phase of your implementation, take advantage of all PeopleSoft sources of information,including the installation guides, table-loading sequences, data models, and business process maps. Acomplete list of these resources appears in thePeopleSoft 8.8 Application Fundamentals for FMS, ESA,and MFGwith information about where to find the most current version of each.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “PeopleSoft Application Fundamentals PeopleBook Preface”




CHAPTER 2

Navigating in PeopleSoft General Ledger

This chapter discusses how to navigate in PeopleSoft General Ledger.

Navigating in PeopleSoft General LedgerPeopleSoft General Ledger provides custom navigation pages that contain groupings of foldersthat support a specific business process, task, or user role.

Note. In addition to the PeopleSoft General Ledger custom navigation pages, PeopleSoftprovides menu navigation, and standard navigation pages.

See Also

Using PeopleSoft Applications

Pages Used to Navigate in PeopleSoft General LedgerThis table lists the Custom Navigation pages that are used to navigate in PeopleSoft General Ledger.

Page Name Navigation Usage

General LedgerCenter

Main Menu, General Ledger Access primary General Ledger Center menu options andactivities.

Allocations Click Allocations on the GeneralLedger Center page.

Accesses the Define and Perform Allocations and theReports folders on the Allocations page.

Define and PerformAllocations

Click Define and PerformAllocations on the Allocationspage.

Accesses the Define Allocation Step, the Copy/Rename/Delete Step, Define Allocation Group, and RequestAllocation options on the Define and Perform Allocationspage.

Reports Click Reports on the Allocationspage.

Accesses the Allocation Step, the Allocation Group, and theAllocation Calculation Log options on the Reports page.

Commitment Control Click Commitment Control on theGeneral Ledger Center page.

Accesses the Define Control Budgets, Define BudgetSecurity, Budget Journals, Post Control Budget Journals,Review Budget Activities, Close Budget, BudgetReports, Third Party Transactions, Review Budget CheckExceptions, Archiving Tables folders on the CommitmentControl page.


Navigating in PeopleSoft General Ledger Chapter 2


Archiving Tables Click Archiving Tables on theCommitment Control page.

Accesses Maintain Ledger Criteria, Request ArchiveProcessing, and Review Archive Log options on theArchiving Tables page.

Budget Journals Click Budget Journals on theCommitment Control page.

Accesses the Enter Budget Journals, Import BudgetJournals, Enter Budget Transfer, Request Entry EventProcessor, and Mass Delete Budget Journals options on theBudget Journals page.

Budget Reports Click Budget Reports on theCommitment Control page.

Accesses the Activity Log, Budget Attributes Report,Budget Control Report, Budget Status, Project Expiration,Associated Budgets Report, Budget Checking Status,Budget Key Translations Report, Budget TransactionDetail, Budgets/Actuals Reconciliation, Budgetary ControlTree Audit, Budget Periods Report, and Ledger Detailsoptions on the Budget Reports page.

Close Budget Click Close Budget on theCommitment Control page.

Accesses the Define Budget Period Set, Validate ClosingSet, Mark to Undo, Closing Rules Report, Define ClosingRule, Validate Run Control, Review Calculation Log,Closing Calculation Log Report, Define Closing Set,Process Budget Close, Review Closing Status, and ClosingStatus Report options on the Close Budget page.

Define BudgetSecurity

Click Define Budget Security onthe Commitment Control page.

Accesses the Events, Assign Rule to User ID, RequestBuild, Create Alert Notifications, Field Setup, Assign Ruleto Permission List, Security Report, Rule Definitions,Assign Rule to Dynamic Group, and NotificationPreference options on the Define Budget Security page.

Define ControlBudgets

Click Define Control Budgets onthe Commitment Control page.

Accesses the Budget Definitions, Funding Source, BudgetAttributes, Funding Source Allocation, AssociatedBudgets, and Source Transactions options on the DefineControl Budgets page.

Post Control BudgetJournals

Click Post Control BudgetJournals on the CommitmentControl page.

Accesses the Request Posting, Mark for Unposting, andBudget Ledger Details Report options on the Post ControlBudget Journals page.

Review BudgetActivities

Click Review Budget Activities onthe Commitment Control page.

Accesses the Budget Details, Budgets Overview, LedgerInquiry Set, and Activity Log on the Review BudgetActivities page.

Review BudgetCheck Exceptions

Click Review Budget CheckExceptions on the CommitmentControl page.

Accesses the Purchasing and Cost Management, Projectand Grants, Travel and Expenses, Revenues, AccountsPayable, and General Ledger folders, and the BudgetChecking Status and Budget Exceptions options on theReview Budget Check Exceptions page.

Accounts Payable Click Accounts Payable on theReview Budget Check Exceptionspage.

Accesses the Voucher, Voucher Non-prorated, and VoucherAccounting Line on the Accounts Payable page.


Chapter 2 Navigating in PeopleSoft General Ledger


Budget CheckingStatus

Click Budget Checking Statuson the Review Budget CheckExceptions page.

Accesses the Budget Checking Status search page.

Budget Exceptions Click Budget Exceptions on theReview Budget Check Exceptionspage.

Accesses the Budget Exceptions search page.

General Ledger Click General Ledger on theReview Budget Check Exceptionspage.

Accesses the Journal, Payroll, and Generic TransactionEntry options on the General Ledger page.

Project and Grants Click Project and Grants on theReview Budget Check Exceptionspage.

Accesses the Project Journal, Project Pre-Encumbrance,Project Encumbrance and Facilities Administration optionson the Project and Grants page.

Purchasing and CostManagement

Click Purchasing and CostManagement on the ReviewBudget Check Exceptions page.

Access the Requisition, Procurement Card, CostManagement, Purchase Order, Receipt Accrual Expense,Purchase Order Non-prorated, and Receipt AccrualEncumbrance options on the Purchasing and CostManagement page.

Revenues Click Revenues on the ReviewBudget Check Exceptions page.

Accesses the Billing Invoice, Revenue Estimate, and DirectJournal options on the Revenues page.

Travel and Expenses Click Travel and Expenses on theReview Budget Check Exceptionspage.

Accesses the Travel Authorization and Expense Sheetoptions on the Travel and Expenses page.

Consolidate FinancialData

Click Consolidate Financial Dataon the General Ledger Centerpage.

Accesses the Consolidation, Review Results Online,Equitization, Reports, and Load Ledgers folder options.

Consolidation Click Consolidation on theConsolidate Financial Data page.

Accesses the Elimination Sets, Consolidation LedgerSets, Subsidiary Ownership, Consolidation Set, MinorityInterest Sets, and Request Consolidation options on theConsolidation page.

Equitization Click Equitization on theConsolidate Financial Datapage.

Accesses the Equitization Rules, Equitization Groups, andRequest Equitization options on the Equitization page.

Load Ledgers Click Load Ledgers on theConsolidate Financial Data page.

Accesses the ChartField Mapping Set, ChartField ValueMapping, Publish Ledgers, and Request Ledger Loadoptions on the Load Ledgers page.

Reports Click Reports on the ConsolidateFinancial Data page.

Accesses the Elimination Sets, MinorityInterest Sets,Ownerships Sets, Consolidation Definition, EliminationSets Audit, Minority Interest Elimination/Adjustment,Elimination Out of Balance, Equitization Rules, andEquitization Calculation Log options on the Reports page.




Review ResultsOnline

Click Review Results Online onthe Consolidate Financial Datapage.

Accesses the Consolidation Dashboard, ConsolidationProcess Log, and Equitization Process Log options on theReview Results Online page.

Inquiry Click Inquiry on the GeneralLedger Center page.

Accesses the Journals, Ledgers, and Accounting folderoptions on the Inquiry page.

Accounting Entries Click Accounting Entries on theInquiry page.

Accesses Contributor Relations Accounting, EnterpriseLearning Management Accounting, Entry Event BudgetAccounting, Entry Event GL Adjustment Accounting,Generic Accounting Entries, Payroll Accounting Entries,and Student Financial Accounting Entries options on theAccounting Entries page.

Journals Click Journals on the Inquiry page.Accesses the Journals, Review Journal Status, ReviewStatus Online, Review Standard Journals, and ReviewSuspense Cross Reference options on the Journals page.

Ledgers Click Ledgers on the Inquiry page.Accesses the Ledger, Ledger Group, Ledger PeriodComparison, Compare Across Ledgers, Review SummaryLedger Status, and Define Inquiry Record and Page optionson the Ledgers page.

Journals Click Journals on the GeneralLedger Center page.

Accesses the Create, Standard Journals, SubsystemJournals, Edit, Budget Check, Post, Inquiry, SuspenseCorrection, Open Items, Entry Event, Archive, and Setupfolder options on the Journals page.

Archive Click Archive on the Journalspage.

Accesses the Request Journal Archive and the ReviewArchived Journal Log options on the Archive page.

Budget Check Click Budget Check on theJournals page.

Accesses the Budget Check Journals, Budget CheckingStatus, Budget Exceptions, and Mark Journals for Overrideoptions on the Budget Check page.

Create Click Create on the Journals page.Accesses the Create Journal Entries, Copy Journals, FlatFile Journal Import, and Spreadsheet Journal Importoptions on the Create page.

Edit Click Edit on the Journals page. Accesses the Edit Journals and Journal Edit Errors Reportoptions on the Edit page.

Entry Event Click Entry Event on the Journalspage.

Accesses the Entry Event Journals option on the EntryEvent page.

Inquiry Click Inquiry on the Journals page.Accesses the Journals and Review Journal Status options onthe Inquiry page.

Open Items Click Open Items on the Journalspage.

Accesses the Review Status Online, ProcessReconciliation, Maintenance, Open Item ListingReport on the Open Items page.




Post Click Post on the Journals page. Accesses the Mark Journals Posting, Mark Journals forUnposting, Post Journals, and Post Journal SummaryReport options on the Post page.

Setup Click Setup on the Journals page.Accesses the Class, Entry Template, and Source Templateoptions on the Setup page.

Standard Journals Click Standard Journals on theJournals page.

Accesses the Define Standard Journals, Create StandardJournals, Review Standard Journals options on the StandardJournals page.

Subsystem Journals Click Subsystem Journals on theJournals page.

Accesses the Accounting Entry Definition, the JournalGenerator Template, and the General Journals options onthe Subsystem Journals page.

Suspense Correction Click Suspense Correction on theJournals page.

Accesses the Correct Suspense Entries, Review SuspenseCross Reference, and Suspended Activity Report optionson the Suspense Correction page.

Ledgers Click Ledgers on the GeneralLedger Center page.

Accesses the Definition, Summary, Closing, AverageDaily Balance, Import/Export, Archive, Ledger DefinitionReports, Ledger Reports, and ADB Reports folder optionson the Ledgers page.

ADB Reports Click ADB Reports on theLedgers page.

Accesses the ADB Definition Report and ADB CalculationReport options on the ADB Reports page.

Archive Click Archive on the Ledgerspage.

Accesses the Request Ledger Archive and ReviewArchived Ledger Log options on the Archive page.

Average DailyBalance

Click Average Daily Balance onthe Ledgers page.

Accesses the ADB Definition and ADB Process options onthe Average Daily Balance page.

Closing Click Closing on the Ledgerspage.

Accesses the Closing Rules, Request Ledger Close, andClosing Rule Report on the Closing page.

Definition Click Definition on the Ledgerspage.

Accesses the Ledger Templates, Detail Ledgers, LedgerGroups, and Ledger Codes options on the Definition page.

Import/Export Click Import/Export on theLedgers page.

Accesses the Import Ledger from Flat File, LedgerFile Formats, and Export Ledger Data options on theImport/Export page.

Ledger DefinitionReports

Click Ledger Definition Reportson the Ledgers page.

Accesses the Template Report, Detail Ledger Report,Ledger Codes Report, and Summary Ledger DefinitionReport options on the Ledger Definition Reports page.

Ledger Reports Click Ledger Reports on theLedgers page.

Accesses the Summary Ledger Detail Report, Closing TrialBalance, and Journal Closing Status Report options on theLedger Reports page.

Summary Click Summary on the Ledgerspage.

Accesses the Ledger Set for Summary Ledger, SummaryLedger Definition, Build Summary Ledger, and ReviewSummary Ledger Status options on the Summary page.




Monitor BackgroundProcesses

Click Monitor BackgroundProcesses on the General LedgerCenter page.

Accesses the Journal Unlock, Non-Shared TableMaintenance, Shared Table Statistics, and BackgroundProcess Report options on the Monitor BackgroundProcesses page.

Process Multi-Currency

Click Process Multi-Currency onthe General Ledger Center page.

Accesses the Define and Process and Reports folder optionson the Process Multi-Currency page.

Define and Process Click Define and Process on theProcess Multi-Currency page.

Accesses the Revaluation Step, Translation Rules,Translation Steps, Translation Within Ledgers, DefineProcess Group, and Request Process options on the Defineand Process page.

Reports Click Reports on the ProcessMulti-Currency page.

Accesses the Revaluation Step, Revaluation CalculationLog, Translation Step, Translation Calculation Log,Translation in Ledger, Translation in Ledger CalculationLog, Translation Ledger In-Sync, and Translation LedgerReconcile options on the Reports page.

Regulatory LedgerReports

Click Regulatory Ledger Reportson the General Ledger Centerpage.

Accesses the Definition, Mapping Structure, MappingRules, Submission Information, Build Regulatory Ledger,Ledger File Extract, Review Ledger Errors, ReviewLedgers, Ledger Errors, and ChartField Value Mappingoptions on the Regulatory Ledger Reports page.

Reporting Click Reporting on the GeneralLedger Center page.

Accesses the General Reports, Federal Reports, and XBRLfolder options on the Reporting page.

General Reports Click General Reports on theReporting page.

Accesses the GL Subsystem Reconciliation folder optionand the Ledger Activity, Ledger Activity with Attribute,Journal Entry Detail, Ledger vs Journal Integrity, StandardJournals, InterUnit Activity, Trial Balance, LedgerSummary, nVision Scope, nVision Request Summary,Build Ledger Cubes, Journal Entry with Attributes, andJournal Line/Accounting Reconciliation options on theReporting page.

GL SubsystemReconciliation

Click GL SubsystemReconciliation on the GeneralReports page.

Accesses the Load Reconciliation Data, Reconciliation bySystem Source, and Reconciliation by ChartFields optionson the GL Subsystem Reconciliation page.

Federal Reports Click Federal Reports on theReporting page.

Accesses the FACTS I, FACTS II Definition, FACTSII Creation, FACTS II Review, FACTS II Reports,SF224/1219/1220, and Fund Balance Reconciliation folderoptions and the Define Reimbursable Account, FederalTransaction Register, and Federal Trial Balance options onthe Federal Reports page.

FACTS I Click FACTS I on the FederalReports page.

Accesses the Define FACTS Tree Group, Load FACTSI Data, Review FACTS I MAF, and Generate FACTS Ioptions on the FACTS I page.

FACTS II Creation Click FACTS II Creation on theFederal Reports page.

Accesses the Create Preparer File, Load MAF Data,Accumulate FACTS II Data, and Create FACTS II File onthe FACTS II Creation page.




FACTS II Definition Click FACTS II Definition on theFederal Reports Page.

Accesses the FACTS II Contact Information, AttributeCross Reference, Treasury Symbol Cross Reference,and Miscellaneous ChartFields options on the FACTS IIDefinition page.

FACTS II Reports Click FACTS II Reports on theFederal Reports Page.

Accesses the Ledger with Attributes Report and the FACTSII Trial Balance options on the FACTS II Reports page.

FACTS II Review Click FACTS II Review on theFederal Reports Page.

Accesses the Review MAF Data, Validate FACTS II Data,and Review FACTS II Data options on the FACTS IIReview page.

Fund BalanceReconciliation

Click Fund BalanceReconciliation on the FederalReports page.

Accesses the Define Report Definition, Import TreasuryFiles, and Generate Reconciliation Report options on theFund Balance Reconciliation page.

SF224/1219/1220 Click SF224/1219/1220 on theFederal Reports page.

Accesses the SF224/1220 Report Definition, SF1219Report Definition, Generate SF224/1220 Data, Run SF224Report/Create File, SF224 Transaction Report, Run SF1219Report, Run SF1220 Report, and Create SF1219/1220 Fileoptions on the SF224/1219/1220 page.

XBRL Click XBRL on the FederalReports page.

Accesses the Context, NameSpace, Element, InstanceTemplate, and Create Instance options on the XBRL page.

Standard Budgets Click Standard Budgets on theGeneral Ledger Center page.

Accesses the Budget Journals, Budget Import, EditJournals, Post Journals, Copy Budgets, and MaintainBudgets folder options on the Standard Budgets page.

Budget Import Click Budget Import on theStandard Budgets page.

Accesses the Flat File Journal Import, Spreadsheet JournalImport, and Budget Journal Import options on the BudgetImport page.

Budget Journals Click Budget Journals on theStandard Budgets page.

Accesses the Create Journal Entry and Copy Journaloptions on the Budget Journals page.

Copy Budgets Click Copy Budgets on theStandard Budgets page.

Accesses the Budget Copy Definition, Budget Copy Group,Request Budget Copy, and Budget Copy Calculation Logoptions on the Copy Budgets page.

Edit Journals Click Edit Journals on theStandard Budgets page.

Accesses the Edit Journals and Journal Edit Errors Reportoptions on the Edit Journals page.

Maintain Budgets Click Maintain Budgets on theStandard Budgets page.

Accesses the Detail Budget Maintenance and Detail ProjectMaintenance options on the Maintain Budgets page.

Post Journals Click Post Journals on theStandard Budgets page.

Accesses the Mark Journals for Posting, Mark Journals forUnposting, Post Journals, and Posted Journals SummaryReport options on the Post Journals page.




SystemConfigurations

Click System Configurations onthe General Ledger Center page.

Accesses the Installation/User Preference, Security,Business Unit Related, Calendars/Schedules, Currency,Design ChartFields, Document Sequencing, Entry Event,Journal Option, Subsystem Journals, Value Added Tax, andMiscellaneous folder options on the System Configurationspage.

Business Unit RelatedClick Business Unit Related on theSystem Configuration page.

Accesses the BU/OpenPeriods/SetID, Ledger, andInter/IntraUnit folder options on the Business Unit Relatedpage.

BU/Open Periods/SetID

Click BU/Open Periods/SetID onthe Business Unit Related page.

Accesses the General Ledger Definition, Ledgers For AUnit, Maintain Process Date, Open Period Display, OpenPeriod Update, Open Periods Mass Update, TableSet IDs,Record Group, TableSet Control, General Ledger Unit, andLedgers For A Unit options on the BU/Open Periods/SetIDpages.

Inter/Intra Unit Click Inter/Intra Unit on theBusiness Unit Related page.

Accesses the System Transaction Definition, TransactionCode, System Transaction Map, InterUnit Pair, InterUnitPair Mass Maintenance, InterUnit Template, IntraUnitTemplate, and Setup Validation options.

Ledgers Click Ledgers on the BusinessUnit Related page.

Accesses the Templates, Detail Ledgers, Ledger Groups,Ledger Codes, Template Report, Detail Ledger Report, andLedger Codes Report options on the Ledgers page.

Calendars/Schedules Click Calendars/Schedules on theSystem Configurations page.

Accesses the Budget Period Calendar, Budget PeriodCalendar Builder, Business Calendar, Calendar Builder,Closure Calendar, Detail Calendar, Detail CalendarReport, Schedules, Schedules Report, Summary BPCalendar, Summary Calendar, Summary CalendarReport, TimeSpans, and TimeSpans Report options on theCalendars/Schedules page.

Currency Click Currency on the SystemConfiguration page.

Accesses the Currency Code, Currency Quotation Method,Market Rate Type, and Market Rates options on theCurrency page.

Design ChartFields Click Design ChartFields on theSystem Configuration page.

Accesses the ChartField Definition, ChartField Reports,and Combination Editing folder options on the DesignChartFields page.

ChartField Definition Click ChartField Definition on theDesign ChartFields page.

Accesses the Account Balancing Group, Account Types,Attributes, ChartField Values, Setup ChartField Value Sets,Review Alternate Account Mapping, and SpeedTypesoptions on the ChartField Definition page.

ChartField Reports Click ChartField Reports on theDesign ChartFields page.

Accesses the Account Balancing Group, Account Types,Alternate Account Cross Reference, ChartField Attributes,ChartField Reports, and SpeedTypes options on theChartField Reports page.




Combination Editing Click Combination Editing on theDesign ChartFields page.

Accesses the ChartField Editing Template, CombinationDefinition, Combination Rule, Combination Group,Combination Rule Report, Combination Group Report,Build Combination Data, Combo/Copy/Rename/Delete,Review Budgets Combo Data, Review Combination Data,Review Combination Build, and Review CombinationSelector Table Data options on the Combination Editingpage.

DocumentSequencing

Click Document Sequencing onthe System Configuration page.

Accesses the Document Type, Document Type Report,Journal Code, Journal Code Report, Journal Type, JournalType Report, Sequence Range, and Sequence Range Reportoptions on the Document Sequencing page.

Entry Event Click Entry Event on the SystemConfiguration page.

Access the Code Definition, Process, Source, and StepDetail Report options on the Entry Event page.

Installation/UserPreference

Click Installation/User Preferenceon the System Configuration page.

Accesses the Installation Options, Installation OptionsReport, Define User Preferences, and User PreferencesReport options on the Installation/User Preference page.

Journal Options Click Journal Options on theSystem Configuration page.

Accesses the Class, Class Report, Entry Template, EntryTemplate Report, Source, and Source Report options on theJournal Options page.

Miscellaneous Click Miscellaneous on theSystem Configuration page.

Accesses the Units of Measure, Units of Measure Report,and Position Accounting options on the Miscellaneouspage.

Security Click Security on the SystemConfiguration page.

Accesses the Security Options, User by User ID, Unitby Permission List, TableSet by User ID, TableSet byPermission List, Ledger by User ID, Ledger by PermissionList, Book by User ID, Book by Permission List, PayCycle by User ID, Pay Cycle by Permission List, Projects,Security View Name, Apply Security Setup, ChartFieldPagelet Security, nVision Ledger Security, Grants Security,Proposal Management Security, Problem Instance by UserID, and Problem Instance by Permission List options on theSecurity page.

Subsystem Journals Click Subsystem Journals on theSystem Configuration page.

Accesses the Accounting Entry Definition and JournalGenerator Template options on the Subsystem Journalspage.

Value Added Tax Click Value Added Tax on theSystem Configuration page.

Accesses the VAT Transaction Type, Express VATCode, VAT Authority, VAT Code, Accounts by BusinessUnit, VAT Country, VAT Entity, VAT Use Type, VATApportionment, VAT Defaults, Service VAT TreatmentDefaults, Business Unit Interunit Option, Business UnitInterunit Pairs, VAT Report Definition, and VAT ReturnXML Data options on the Value Added Tax page.



PeopleSoft General Ledger Business ProcessesEach of these General Ledger business processes is covered in the PeopleSoft General Ledger PeopleBook.

• Allocations (FS_ALLC)

• Combo Edit Build (FS_CEBD)

• ChartField Combination Editing (FS_CEDT_PROC)

• Journal Generator (FS_JGEN)

• Ledger Archive (GL_ADB_ARCH)

• ADB Calculation (GL_ADB_CALCX)

• Post Daily Balance (GL_ADB_POST)

• Spreadsheet Journal Import (GL_EXCL_JRNL)

• Journal Edit (GL_JEDIT)

• Journal Archive (GL_JRNL_ARCH)

• Journal Copy (GL_JRNL_COPY)

• Flat File Journal Import (GL_JRNL_IMP)

• Flat File Ledger Import (GL_LED_IMP)

• Ledger Load (GL_LED_LOAD)

• Standard Journal Entry (GL_SJE)

• Commitment Control Budget Closing (FSPYCLOS)

• Commitment Control Budget Post (FSPQPOST)

• Commitment Control Budget Processor (FSPKBDP3)

• Commitment Control Archive (FS_KKAR)

• Closing (GLPCLOSE)

• Consolidations (GLPOCONS)

• Equitization (GLPQEQTZ)

• Journal Post (GLPPPOST)

• Multicurrency Processing (FSPCCURR)

• Open Item Reconciliation (GLPPOITM)

• Summary Ledger (GL_SUML)

Note. The processes listed here are the main GL processes (AE or COBOL). PeopleSoft General Ledger alsohas some AE or SQR processes that are mainly for loading data to do government reporting ( FACTS I,FACTS II, SFxxx). Since these are more like a report than a process, they are not included in this list.



You can also access these options through the portal menu options by clicking the General Ledger menuoption and then clicking the appropriate business process menu option. The selected business processmenu option lists all the options associated with the selected business process.

We cover these business processes in the business process chapters of this General Ledger PeopleBook.

PeopleSoft General Ledger IntegrationsPeopleSoft General Ledger serves as the core of the PeopleSoft Financial Management System. ThePeopleSoft subsystem applications, such as Payables and Receivables, create accounting entries that you selectto process in the journal generator. Journal generator creates the appropriate journals from the accountingentries and sends them to General Ledger for posting to the appropriate ledgers. From this posted accountingdata, you can obtain both detail and summary accounting information and produce numerous financialreports for your organization. There are three methods of integrating data into General Ledger:

• Selecting the PeopleSoft subsystem application transactions that are then run in journal generator.

• Integrating external PeopleSoft application transactions from HRMS or Learning Solutions that useapplication messages to send data to General Ledger. When you select them in journal generator,the remaining application messages begin processing from there.

• Uploading external application transactions into General Ledger through flat files and thenprocessing them in journal generator to create journals.



External and Subsystem Processing in Journal Generator and General Ledger

PeopleSoft General Ledger integrates with:

• Asset Management

• Commitment Control

• Payables



• Purchasing

• Receivables

• Billing

• Deduction Management

• Expenses

• Treasury

• Cost Management

• Contracts

• Projects

• Grants

• Inventory

• Enterprise Performance Management (EPM)

• Budgeting

• Human Resources Management (HRMS)

- PeopleSoft Payroll

- PeopleSoft Global Payroll

• Learning Solutions

• Enterprise Learning Management (ELM)

Supplemental information about third-party application integrations is located on thePeopleSoft Customer Connection website.

See Also

PeopleSoft Setup Manager for Financials, Enterprise Service Automation, and SupplyChain Management 8.8 PeopleBook

Implementing General LedgerPeopleSoft Setup Manager enables you to generate a list of setup tasks for your organizationbased on the features that you are implementing. The setup tasks include the components thatyou must set up, listed in the order in which you must enter data into the component tables,and links to the corresponding PeopleBook documentation.

PeopleSoft General Ledger also provides component interfaces to help you load data from youexisting system into PeopleSoft General Ledger tables. Use the Excel to Component Interfaceutility with the component interfaces to populate the tables.

The Component Interface Table for lists all of the components that have component interfaces usingGeneral Ledger tables. Since this component data is used for many PeopleSoft applications, thetable appears in thePeopleSoft Application Fundamentals PeopleBook



SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Getting Started With PeopleSoftApplication Fundamentals,” Implementation Considerations.

Other Sources of Information

In the planning phase of your implementation, take advantage of all PeopleSoft sources of information,including the installation guides, table-loading sequences, data models, and business process maps. Acomplete list of these resources appears in thePeopleSoft 8.8 Application Fundamentals for FIN, ESA,and SCMwith information about where to find the most current version of each.

See Also

PeopleSoft Setup Manager for Financials, Enterprise Service Automation, and SupplyChain Management 8.8 PeopleBook

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “PeopleSoft Application Fundamentals PeopleBook Preface”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Getting Started With PeopleSoft Application Fundamentals”


CHAPTER 3

Defining Your Operational Structure

This chapter provides an overview of PeopleSoft General Ledger business units andoptions and discusses how to:

• Define PeopleSoft General Ledger business units.

• Define journal processing options for a business unit.

• Define currency options for a business unit.

• Define approval options for a business unit.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Using Interunit and Intraunit Accounting andChartField Inheritance,” Specifying Interunit and Intraunit Settings for General Ledger Business Units

Chapter 13, “Processing Value Added Tax (VAT) Transactions in PeopleSoft General Ledger,”Setting Up General Ledger Business Unit VAT Default Options , page 246

Understanding PeopleSoft General Ledger BusinessUnits and Options

Before you implement PeopleSoft General Ledger, examine how the business operates—that is, how work isperformed—and decide how you want to map the operational business structures to General Ledger.

This section lists prerequisites and discusses:

• PeopleSoft General Ledger business units.

• Average daily balance (ADB) incremental calculation method.

• Journal processing options for a business unit.

• Value-added tax (VAT) options.

PrerequisitesBefore you set up business units, decide on the tableset structure and set up your setIDs.

Before you set up the Balance Suspense, Edit Suspense, and Amount Suspense ChartFields,define the account balancing groups.


Defining Your Operational Structure Chapter 3

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Creating Account Balancing Groups

PeopleTools PeopleBook: Application Designer, "Creating Record Definitions"

PeopleSoft General Ledger Business UnitsWhen you define the operational business structure that a PeopleSoft General Ledger business unitrepresents, keep in mind the functions that correspond to individual business units:

• Entering, approving, and maintaining journal transactions.

• Requesting background processing.

• Requesting reports.

• Defining ChartFields.

• Creating interunit journal transactions.

• Defining journal entry error and approval processing.

• Specifying a single base currency.

• Specifying tableset sharing.

• Enforcing security.

ADB Incremental Calculation MethodWhen you create a run control request for ADB calculation, you select an ADB definition and period type. Ifthe values that you enter on the run control match a specified ADB definition and period type combination,the process uses the incremental calculation method. Otherwise, the system uses the ad hoc method.

Journal Processing Options for a Business UnitWhen you define a business unit, you can determine how the system processes a journal entry for that businessunit. In PeopleSoft General Ledger, you can specify these processing options at the business unit, ledger, orjournal entry source level. Processing options defined for a ledger override those defined for a businessunit. Options defined for a source override those defined for both a ledger and business unit.

Set journal options for the following types of errors:

Journal Balance Errors When you define ledgers, specify them as balanced or unbalanced.Journal entries for balanced ledgers, such as an actuals ledger, mustbe in balance before posting. A journal balance error occurs when anunbalanced journal is targeted to a balanced ledger.

Journal Edit Errors When you edit journals, PeopleSoft General Ledger verifies that allChartField values are valid as of the journal date. A journal edit error occursif you enter an invalid ChartField value or combination on the journallines. This error category also includes other line errors, such as a blankcurrency code or an invalid OpenItem reference value.


Chapter 3 Defining Your Operational Structure

Control Total Errors When you edit journals, any amounts entered on the Journal Entry Totals pageare checked against the actual totals of the journal line amounts.

Journal Amount Errors Foreign amounts and monetary amounts in a journal line musthave the same sign. This error processing verifies that all amountsare either positive or negative.

Journal Date Errors The journal date is validated against the open period. An error is generated ifthe journal date entered is not within the specified open period.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Specifying Journal Source Error Processing

VAT OptionsTo enable VAT processing in PeopleSoft General Ledger, you must first set up your VATenvironment. VAT setup in General Ledger involves setting defaults and parameter controls andapplying them at the business unit, journal source, and account levels.

See Also

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Working with Value Added Taxes (VAT)”

Chapter 13, “Processing Value Added Tax (VAT) Transactions in PeopleSoft General Ledger,” page 237

Defining PeopleSoft General Ledger Business UnitsTo define PeopleSoft General Ledger business units, use the General Ledger Definitioncomponent (BUS_UNIT_TBL_GL). Your business practices determine how to set up GeneralLedger business units and the journal processing options.

This section discusses how to:

• Define a PeopleSoft General Ledger business unit.

• Define PeopleSoft General Ledger business unit ID numbers.

• Specify an ADB incremental calculation method.



Pages Used to Define PeopleSoft General Ledger Business Units

Page Name Object Name Navigation Usage

General Ledger Definition -Definition

BUS_UNIT_TBL_GL1 Set Up Financials/SupplyChain, Business UnitRelated, General Ledger,General Ledger Definition,Definition

Define a PeopleSoft GeneralLedger business unit.

Business Unit ID Numbers BU_ID_NBRS_GL_SEC Click a business unit IDnumber on the GeneralLedger Definition -Definition page.

Enter the ID for the reportingentity for a business unit.

Incremental CalculationMethod

BU_ADB_INCR_SEC Click the ADB IncrementalCalc Method (ADBincremental calculationmethod) link on the GeneralLedger Definition -Definition page.

Identify the ADBdefinition and period typecombinations that the systemruns regularly, and use theincremental method tocalculate average balances.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining Accounting Calendars,” Defining Business Calendars

Defining a PeopleSoft General Ledger Business UnitAccess the General Ledger Definition - Definition page.

General Ledger Definition - Definition page

Base Currency Enter a code for theonlyprimary currency for the PeopleSoft General Ledgerbusiness unit. The base currency is sometimes referred to as thebookcurrency.It is usually the local currency for the organization, although it can be different.

As of Date Enter a date that is the benchmark for the system’s current reporting periodand calculations of year-to-date amounts. The as-of date is a report option onPS/nVision report requests. When you change the as-of date for a business



unit, all reports using this option run relative to the as-of date that you specifyhere, so it is not necessary to change the report specifications.

Default SetID Enter a setID to determine the preliminary tableset sharing setup for thebusiness unit. This field does not appear after the business unit is created.

Create BU (create businessunit)

Click to create a new business unit. After you create the businessunit, this button is not available.

Holiday List Select to identify holiday calendars for different countries or business units.Several PeopleSoft General Ledger processes—including the Journal Postprocess, the Journal Entry process, and many others—use this calendar todetermine working days and limit journal dates to working days only.

Customer Vendor Affiliate Select to obtain the interunit ChartField value from the customer or vendortables when you create a transaction for the business unit.

Enable DocumentSequencing

Select to use document sequencing for business units that operatein a country requiring it. You can track journal entries by documentsequence number, if desired.

Consol - For EliminationsOnly (consolidate - foreliminations only)

To automate the elimination of intercompany transactions, select toset up this special type of PeopleSoft General Ledger business unit asan eliminations entity for consolidations processing.

Defining PeopleSoft General Ledger Business Unit ID NumbersAccess the Business Unit ID Numbers page.

Standard ID Qualifier Select the qualifier for the type of reporting entity.

ID Num (ID number) Enter the ID number for the reporting entity for the business unit.

Specifying an ADB Incremental Calculation MethodAccess the Incremental Calculation Method page.

Incremental Calculation Method page

Average Daily Balances Select an ADB definition from a list of definitions on the AverageDaily Balance Definition - Definition page.



Select only ADB definitions that you run regularly (for example,month-to-date averages).

Period Type Select a period type to associate with the definition. Values are:

Date to Date:Calculates ADBs from a beginning date to the run request date.

Month to Date:Calculates ADBs from the first day of the month (which is thebeginning date of the accounting period in which the run request date falls)to the run request date. To use this option, the detail ledger for the businessunit must be tied to a detail calendar that uses monthly periods.

Quarter to Date:Calculates ADBs from the first day of the quarter(the beginning date of the first accounting period in the quarter inwhich the run request date falls) to the run request date. To use thisoption, the detail ledger for the business unit must be tied to a detailcalendar that uses monthly periods 1 through 12.

Regular Date:Calculates average balances for the date range specifiedon the Average Daily Balance Process - Request page.

Regular Period:Calculates ADBs for a specified period range in aspecified fiscal year. The calculations use the beginning date of aFrom period to the ending date of a To period.

Year to Date:Calculates ADBs from the first day of the year (which is thebeginning date of accounting period 1) to the run request date.

See Also

Chapter 14, “Calculating Average Balances,” Processing Average Daily Balances, page 272

Chapter 14, “Calculating Average Balances,” Identifying the Ledgers, page 267

Chapter 14, “Calculating Average Balances,” Understanding Average Balance Calculation, page 255

Defining Journal Processing Options for a Business UnitTo define journal processing options for business units, use the General Ledger Definition component.


• Define journal processing options.

• Specify balance suspense ChartFields.

• Specify edit suspense ChartFields.

• Specify amount suspense ChartFields.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Creating Account Balancing Groups.



Pages Used to Define Journal Processing Optionsfor a Business Unit


Journal Options BUS_UNIT_TBL_GL2 Set Up Financials/SupplyChain, Business UnitRelated, General Ledger,General Ledger Definition,Journal Options

Specify how the systemhandles the journal errorprocessing options for abusiness unit and how thesystem determines theprocess date for journalprocessing.

Balance SuspenseChartFields

BU_JE_BS_CFS_SEC Click the Balance SuspenseChartFields link on theJournal Options page.

Specify the suspenseChartFields for balancingerrors for a business unit.

Edit Suspense ChartFields BU_JE_ES_CFS_SEC Click the Edit SuspenseChartFields link on theJournal Options page.

Specify the suspenseChartFields for journal editerrors for a business unit.

Amount SuspenseChartFields

BU_JE_AS_CFS_SEC Click the Amount SuspenseChartFields link on theJournal Options page.

Specify the suspenseChartFields for journalamount errors for a businessunit.

Defining Journal Processing OptionsAccess the Journal Options page.

Journal Options page

Journal Balance Option Specify how the system handles balancing errors for thebusiness unit. Values are:

Recycle:Marks journal containing this error as invalid and preventsyou from posting them. Once you’ve made the corrections and reeditedthe journal, you can post the journal successfully.

Suspend:Posts the amount required to bring each journal intobalance to suspense ChartFields.

Balance SuspenseChartFields

Click to access the Balance Suspense ChartFields page.



Journal Edit Errors Option Specify how the system handles journal edit errors for thebusiness unit. Values are:

Recycle:Marks journal entries containing errors as invalid and preventsyou from posting them. Once you’ve made the corrections and reeditedthe journal, you can post the journal successfully.

Suspend:Moves the journal entry amounts containing errors intosuspense ChartFields and enables you to continue with the posting.Access the Edit Suspense ChartFields page to specify the ChartFieldsand ChartFields values that need to be suspended.

Edit Suspense ChartFields Click to access the Edit Suspense ChartFields page.

Control Total Option Specify how the system handles control total errors for thebusiness unit. Values are:

Recycle:Marks journal containing control total mismatches as invalid andprevents you from posting them. Once you’ve made the corrections or changedthe control totals and reedited the journal, you can post the journal successfully.

N/A: Excludes any control totals previously set. TheN/A option isavailable only for control total errors.

Journal Amount ErrorsOption

Specify how the system handles errors when the foreign amounts and themonetary amounts do not have the same sign. For example, the system mustdetermine how to handle errors for a journal that has a foreign amount thatis 10.00 GBP and the monetary amount is -200.00 USD. Values are:

Accept:Accepts the amounts and does not generate an error.

Recycle:Marks journal entries containing errors as invalid and preventsyou from posting them. Once you’ve made the corrections and reeditedthe journal, you can post the journal successfully.

Suspend:Posts the journal to a suspense account with the monetary amountsign reversed. In the preceding example, the suspense line has a foreignamount of 10.00 GBP and a monetary amount of -200.00 USD. Accessthe Amount Suspense ChartFields page to specify the ChartFields andChartField values for the suspense account for balancing errors.

Amount SuspenseChartFields

Click to access the Amount Suspense ChartFields page.

Journal Process Date Specify how processes determine the process date for journals. TheJournal Post process (GLPPPOST) and the Journal Generator process(FS_JGEN)—and many other PeopleSoft General Ledger processes—supportthe use of the Process Date option. Values are:

Current Date:For general ledger processes that use the process date in their runcontrols, select this option to use the date at the time that the batch process runs.

Process Date:Use a date that you specify in the next field for all journalsin the batch. The system permits you to enter only a working calendar day.Before you run any processes that use a process date, you can use the MaintainGL BU Process Date (maintain general ledger business process date) process



to perform a mass update of the journal process date. You can run this processfor an individual business unit, a range of business units, or all business units.

Process Date Specify a process date.

Journal Date < OpenFrom Date

Interunit journals contain multiple journals, one for each related businessunit. Each business unit and its ledger group can have different accountingperiod opening and closing options. A journal date can be open for onebusiness unit, and closed for another. You can make the Journal Editprocess change the journal date if its period is closed, so the journal (ifvalid for all other edits) can be posted to an open period.

When the journal date is less than the open-from date, recycle the journalor change the journal date to the open-from date.

Journal Date > OpenTo Date

When the journal date is greater than the open-to date, either recyclethe journal or change the journal date to the open-to date.

Allow Different UnpostDate

Select to enable users to specify an unpost date for a posted journal. Thisdate becomes the journal date for the unpost journal when the original journalis unposted. The unposting journal carries its original journal date in theUNPOST_JRNL_DATE field. The default is not to allow unpost dates.

For interunit journals, users cannot change an unpost date if any ofthe business units are not enabled for this. Otherwise, all journalsin the set use the user-specified date.

For suspense correction journals, the system uses the samedate as the base journal.

For reversals, the system uses the original journal date unless theperiod is closed. There is a runtime option for reversal the journaldate if the original period is closed.

See Also

Chapter 10, “Processing Journals,” Posting Journals, page 204

Specifying Balance Suspense ChartFieldsAccess the Balance Suspense ChartFields page.

Specify the entire ChartField combination for suspense entries for balancing errors.

Group Specify the account balancing group to distinguish balance-sheetaccounts from off-balance-sheet accounts.

ChartField Specify the type of ChartField (such as Account or Department) forsuspense entries for balancing errors.

ChartField Value Specify the ChartField value for suspense entries for balancing errors.

Specifying Edit Suspense ChartFieldsAccess the Edit Suspense ChartFields page.



Specify the entire ChartField combination for suspense entries for journal edit errors.

See Also

Chapter 3, “Defining Your Operational Structure,” Specifying Balance Suspense ChartFields, page 33

Specifying Amount Suspense ChartFieldsAccess the Amount Suspense ChartFields page.

Specify the entire ChartField combination for suspense entries for journal amount errors.

See Also

Chapter 3, “Defining Your Operational Structure,” Specifying Balance Suspense ChartFields, page 33

Defining Currency Options for a Business UnitTo define currency options for business units, use the General Ledger Definition component.

This section discusses how to define the journal currency options for a business unit.

Page Used to Define Currency Options for a Business Unit


Currency Options BUS_UNIT_TBL_GL3 Set Up Financials/SupplyChain, Business UnitRelated, General Ledger,General Ledger Definition,Currency Options

Specify the journal currencyoptions for a business unit.

Defining Currency OptionsAccess the Currency Options page.

Currency Balancing Option Specify how journal lines are balanced for a particular business unit. Values are:

Balance by All Currencies:Balances by individual transaction currencytype. For example, all lines in British pounds are balanced together, and alllines in Mexican pesos are balanced together. Select this option when theKeep Ledgers in Sync option is selected for the ledger group.

Balance by Base Currency Only:Balances all journal linesby the base currency only.

Base Currency AdjustOption

Select to control manual adjustments to the base currency in foreigncurrency journals for a particular business unit. Values are:

Allow Base Curr Adjustments(allow base currency adjustments): Enables youto directly change the base currency amount on foreign currency journal lines.



Disallow Base Cur Adjustments(disallow base currency adjustments):Prevents you from directly changing the base currency amounton foreign currency journal lines.

Foreign Currencies perJournal

Select to control the number of foreign currencies for each journalfor a particular business unit. Values are:

Multiple Foreign Currencies:Allows journals to contain linesin multiple foreign currencies.

Only One Foreign Currency:Allows journals to contain lines onlyin the base currency and a single foreign currency. You must specifythe foreign currency in the journal header.

No Foreign Currencies:Allows journals to contain lines onlyin the base currency.

Defining Approval Options for a Business UnitTo define approval options for business units, use the General Ledger Definition component.

This section discusses how to specify journal entry approval options for a business unit.

Page Used to Define Approval Options for a Business Unit


Approval Options BUS_UNIT_TBL_GL4 Set Up Financials/SupplyChain, Business UnitRelated, General Ledger,General Ledger Definition,Approval Options

Specify journal entryapproval options for abusiness unit.

Defining Approval OptionsAccess the Approval Options page.



Approval Options page

Journal Approval Option Select an option for standard journals. Values are:

Pre-Approved:Allows journal entry without approval through PeopleSoftWorkflow. The Post Journal option is available on the Journal Entry - Line page.

Specify Approval Rule:Requires approval through PeopleSoft Workflow. Ifyou select this option, enter the business process name and the approval ruleset that you created using PeopleSoft Application Designer. The SubmitJournal option is available on the Journal Entry - Line page.

Budget Journal ApprovalOptn (budget journalapproval option)

For budget journals, select eitherPre-Approvedor Specify ApprovalRuleas defined for the Journal Approval Option field.

See Also

Chapter 22, “Approving Journal Entry,” Understanding the Journal Entry Approval Process, page 465


CHAPTER 4

Using Statistics

This chapter provides an overview of statistical journals and discusses how to:

• Set up for journal entries using statistics.

• Create journal entries using statistics.

Understanding Statistical JournalsIn PeopleSoft General Ledger, you can use statistical data to facilitate financial analysis and reporting,as well as to form the basis for allocating certain expenses. You can use statistic codes to tracknonmonetary amounts, to allocate expenses such as overhead to products, or to calculate a ratio ofexpense versus the number of customers for a regional expense analysis.

Units of measure determine how to quantify the statistical amount entered on a journal. You mustassociate each statistical account or statistics code with a standard unit of measure. This controlsthe units that appear in reports and enables the automatic conversion feature.

Automatic conversion enables you to post journal entries in whatever unit is convenient during journal entry.The system automatically converts entered units to standard units—for example, square yards to square feet.To do this, use the Convert To and Conversion Rate entries on the Units of Measure page. During journalentry, when you enter the statistical amount in square yards, the system converts that amount to square feetautomatically, a system message confirms it, and the journal line stores the amount in square feet.

You can use one of two methods to implement statistics:

• Use a statistical ledger containing statistical accounts in your journal entries.

• Use statistics codes associated with monetary accounts.


• Statistical ledger and accounts method.

• Statistics code method.

PrerequisitesDepending on how you want to perform statistical accounting, you must define:

• Units of measure.

• A statistical ledger and statistical account, if you want to use the statistical accountmethod of statistical accounting.


Using Statistics Chapter 4

• Statistics codes, if you want to use the statistic code method of statistical accounting.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Understanding Ledgers

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Entering Units of Measure

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Defining a Detail Ledger

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining and Using ChartFields”

Statistical Ledger and Accounts MethodDefine a separate ledger to track only statistical data to segregate the statistical information fromactual, budget, or other types of monetary information by ledger. To define a statistical ledger, youdefine a new ledger as you would any other ledger and only post statistical amounts to that ledger.If you use this method, you must use statistical accounts in your journal entries.

Define a statistical account and associate it with a unit of measure. For example, the Workstationsstatistical account usesEA. (each) as a generic unit of measure. The Floor Space statistical accountmight useSQ.(square feet), while the Work Days account would useDAY (days).

You enter two separate journal entries to accommodate the statistical monetary amount of a transaction. Forexample, if you purchase 100 workstations, the journal entry that records the purchase includes a line for thestatistical entry (100 workstations) and an additional journal entry to record the monetary amount.

Statistics Code MethodAn alternate way to track statistical amounts is by using statistics codes. This eliminates the need toenter an additional journal entry when there are statistics associated with the transaction. This is becauseyou associate a statistics code with a monetary account. As with other ChartFields, there is a table ofvalid statistics codes that you can add or update on the Statistics Codes page. These can include itemssuch as floor space, full-time equivalent workdays, shipment size, or generic units.

You create a journal entry where you enter the statistics on the same journal line asthe corresponding monetary entry.

For example, using this method, a journal line that records the charge-back of rent expense toan individual department can include the dollar amount of the rent to be charged and the amountof floor space used to determine the charge all on one line.

Setting Up for Journal Entries Using StatisticsThis section discusses how to:


Chapter 4 Using Statistics

• Set up for journal entries using statistical accounts.

• Set up for journal entries using statistics codes.

Pages Used to Set Up for Journal Entries Using Statistics


Units of Measure UNITS_OF_MEASURE Set up Financials/SupplyChain, Common Definitions,Units of Measure, Units ofMeasure

Set up codes anddescriptions for units ofmeasure.

Account GL_ACCOUNT Set up Financials/SupplyChain, Design ChartFields,Define Values, ChartFieldValues, Account

Identify the accountChartField values that youwant to use as statisticalaccounts.

Statistics Code STATISTICS_TBL Set up Financials/SupplyChain, Design ChartFields,Define Values, ChartFieldValues, Statistics Code

Set up statistics codeChartField values.

Setting Up for Journal Entries Using Statistical AccountsTo set up for journal entries using statistical accounts:

1. Set up the Unit of Measure (UOM) values (or select one that you want to associatewith selected account ChartField values.

Note. PeopleSoft data delivered with your product contains many UOM values.

2. Select the Statistical Accounting check box and a UOM value on the ChartField Value - Accountpage for accounts in which you want to track statistical values.

Setting Up for Journal Entries Using Statistics CodesTo set up for journal entries using statistics codes:

1. Set up the Unit of Measure (UOM) values (or select one that you want to associatewith selected account ChartField values.

Note. PeopleSoft data delivered with your product contains many UOM values.

2. Add the statistics codes ChartFields that you want to use to track your data on the Statistics Codes page.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining Financials and SupplyChain Management Common Definitions,” Entering Units of Measure.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions,Enterprise Service Automation, and Supply Chain Management PeopleBook, “Defining andUsing ChartFields,” Adding Statistics Code Values.



Creating Journal Entries Using StatisticsThis section discusses how to:

• Create statistical journal entries using statistical accounts.

• Create statistical journal entries using statistics codes.

Page Used to Create Statistical Journal Entries


Create Journal Entries- Lines

JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries, Lines

Record both monetary andstatistical debit and creditamounts.

Creating Statistical Journal Entries Using a Statistical AccountsAccess the Create Journal Entries - Lines page.

1. Access Create Journal Entries - Lines page and debit and credit the statistical account ChartFields.Enter the amount based on the UOM that you set up in the account ChartField.

2. Create a second journal entry for the monetary accounts and amounts associatedwith the previous statistical journal entry.

3. When you process these journal entries, the statistical data is posted in the statistical ledgerassociated with the business unit and the monetary amounts are posted to the appropriatemonetary ledgers associated with the business unit.

When you create a journal entry using a statistical ledger and statistical account ChartFields, theinformation described for the following fields on the journal line applies:

Stat (statistic) This field is not available for entry. It is only enabled whenusing the statistic code method.

Stat Amt (statistical amount) Enter the total number of units that are involved in the transaction.

UOM (unit of measure) The unit of measure automatically appears based on the unit of measure thatyou select when you set up the statistical account ChartField.

See Chapter 8, “Making General Ledger Journal Entries,” page 107.

Creating Statistical Journal Entries Using Statistics CodesAccess the Create Journal Entries - Lines page.

Enter the data for this journal line, including monetary data, and use the following guidelinesto select a statistics code and its relevant data.

Stat (statistic) Select a code.

Stat Amt (statistical amount) Enter the total number of units that are involved in the transaction.


Chapter 4 Using Statistics

UOM (unit of measure) The unit of measure automatically appears based on the selected statistics code.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Creating Journal Entries, page 110




CHAPTER 5

Understanding General Ledger BackgroundProcesses

This chapter discusses:

• The background process model.

• Initiation of processes from application pages.

• Restart and recovery of processes.

• Process concurrency.

The Background Process ModelMany functions in PeopleSoft General Ledger, such as journal editing and posting, allocationsprocessing, financial consolidations, year-end closing, and creation of summary ledgers are run asbackground processes using a process request page. A common processing model is incorporatedinto all PeopleSoft background processes to initiate processes, monitor their progress, and track theirhistory. In addition, through commits, this model frees shared resources as quickly as possible tofacilitate concurrent activity. The model includes the following elements:

• Unit of work.

• Process instance (run ID).

• Request records.

• Message log.

See Also

PeopleSoft PeopleTools PeopleBook: Process Scheduler, Understanding PeopleSoft Process Scheduler

Unit of WorkThe unit of work is the interval of processing that takes place between commit points. All PeopleSoft GeneralLedger background processes use a functional approach to defining the unit of work. This guideline is thebasis for the restart and recovery process. If a program encounters an error during the unit of work interval, thesystem rolls back all processing to the previous completed unit of work. If a rollback occurs as a subset ofthe request criteria, this point is indicated on the request record for that background process.


Understanding General Ledger Background Processes Chapter 5

For the Allocations and Year End Close background processes, the unit of work is defined as a subset(a process step) within the request level. The program can successfully complete an allocation stepor close a ledger for a fiscal year without completing all the steps or business units specified in therequest record. The Year End Close process commits the work for each unique ledger and businessunit combination. This enables you to continue an interrupted job by starting from the failed businessunit. In these cases, several commits could be issued before the request record is updated. For theConsolidations and Equitization process, the unit of work is the same as the request level.

The amount of time required to complete a unit of work is critical when determining which processes can runconcurrently. Because this is a function of the data, the nature of the requests, and the database environment,you should run tests of typical units of work to see how long they take in the absence of conflicting processes.

Process Instance (Run ID)The system assigns a unique process instance number to each background run. The number uniquelyidentifies data within shared work and log tables. The process instance field counter resides inPS_PRCSSEQUENCE.SEQUENCENO. At the start of a background process, a program updates thecounter (incrementing it by 1), selects the value, and then commits the work.

Request RecordsThe request record stores information about the status of a background process. A request record defines theinput data that a background process uses to complete a unit of work, and it contains these fields:

OPRID andRUN_CNTL_ID

Identifies a request set, which can be made up of multiple requests.

REQUEST_NBR orREQUEST_ID

Identifies the individual requests within that request set.

PROCESS_FREQUENCY Indicates whether to process a request every time the request setis processed or only the next time.

PROCESS_STATUS Indicates the success or failure of the request once it is processed.

DTTM_STAMP_SEC Stores the date that the request was last processed.

When a background process starts, it reads the first request record that is flagged for processing.After the record is read, it is immediately updated asIn Processand committed by the backgroundprocess. This prevents other instances of the process from reading and processing the request,and it provides information about the current status.

If the PROCESS_FREQUENCY field value isProcess Once,the process changes the value toDon’tProcesswhen the request is complete. The process updates the PROCESS_STATUS field to reflect thesuccess or failure of the run, and it issues a commit immediately after the update.

Message LogEach background process generates informational and error messages related to the process run.Because all processes share the tables where the system logs these messages, a commit occurs afteran insert into the Message Log table to prevent locking by one process.


Chapter 5 Understanding General Ledger Background Processes

Initiation of Processes from Application PagesSome processes, such as the Journal Edit process and the Journal Post process, can be initiated fromapplication data-entry pages. For example, to initiate the Journal Edit process from the Create JournalEntries - Lines page, select Edit Journal in the Process field. The system initiates the edit backgroundprocess immediately. You use this same method to post and copy a journal on the Lines page.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Specifying Processing Selection Criteria , page 123

PeopleSoft PeopleTools Process Scheduler PeopleBook: “Submitting and Scheduling a Process Request”

Restart and Recovery of ProcessesIf the system encounters an error while processing a request, it performs a rollback and sets thePROCESS_STATUS in the request record toError. The program then continues to process the next request.To rerun the canceled request, you must return to the online request page and reinitiate the request.

Identify any requests marked in error using the message log information. When you correct the conditionthat caused the error, mark the request for processing and run the job again.

Concurrent ProcessingBefore you decide which types of activities occur concurrently within PeopleSoft GeneralLedger, you must understand which tables are accessed by background and reporting processes.The tables accessed by various processes can affect the processes that you run concurrentlywith online activity or with other background programs.

Concurrency is important in the usage of both physical and functional tables:

• Physical usage.

Certain processes bar access to tables required of other processes, so those processes cannot be runconcurrently. Physical usage is based on an analysis of the unit of work anticipated in the environment,along with the type of table access a background or reporting process performs. This depends on theStructured Query Language (SQL) access type. Multiple processes can perform Select access against atable. Delete, Update, and Insert access can cause table or row locking (depending on the platform). Inturn, this might cause a conflicting and concurrently running process to pause or take a time-out.

• Functional usage.



Although a table may be physically available, it might cause problems to make changes while a process isrunning. Consider the elimination set tables used by the Consolidation background process. Functionally,you do not want a user to modify the elimination set definitions online while another user runs theConsolidation process to generate elimination entries. This can result in unexpected or inaccurate resultsfor the user running the background process. User and object security are two system tools that canprovide segregation of functional access to tables online and in the background.

Most of the PeopleSoft General Ledger batch COBOL processes are designed to enableefficient concurrent processing by using nonshared temporary tables to minimize contention onthese tables. Each process has its own temporary table when multiple jobs run concurrently.For example, if two Currency Translation jobs (FSPCCURR) are running, the first job usesCURR_WRK_TBL001 and the second job uses CURR_WRK_TBL002.

PeopleSoft General Ledger provides four temporary tables for each of the processes using nonsharedtemporary tables. The system administrator can add more temporary tables if necessary. Ifall temporary tables are in use—for example, one job is submitted while four other jobs runconcurrently—the shared temporary table (CURR_WRK_TBL in the case of the Currency Translationprocess) is shared by the fifth job and by subsequent jobs submitted.

For Application Engine processes, the number of instances of nonshared temporary tablesis specified in the Application Engine properties. For example, the number of temporarytable instances for the Combo Edit process is set to4.

See Also

Chapter 7, “Optimizing General Ledger Performance,” Using Non-Shared Tables, page 79

Concurrent ProcessesThe PeopleSoft General Ledger Utility processes perform Updates, Deletes, and Inserts, so you must takeconcurrency into account. These processes directly modify and load data into transaction and system tables. Ifyou run these processes, you should be aware of the tables affected and you should run the processes onlyat appropriate times. This table lists identifies the tables used by each function of the process:

Utility Function Tables Used When to Run LockedTables

Commit AfterLoading

GL_EXCL_JRNL

Insert, Update,and Delete

PS-JRNL_HEADER

PS_JRNL_LN

PS_OPEN_ITEM_GL

Anytime Journal tables All data

GLS9001 Insert, Update,and Delete

PS tree tables Do not runconcurrentlywith PeopleSoftTree Managerand PS n/Vision.

Tree systemtables

All data



Utility Function Tables Used When to Run LockedTables

Commit AfterLoading

GL_JRNL_IMP Insert PS_JRNL_HEADER,

PS_JRNL_LN,

PS_JRNL_VAT,

PS_OPEN_ITEM_GL,

PS_JRNAL_CF_BAL_TBL

Anytime Journal tables All data

GL_LED_IMP Insert andDelete

PS_LEDGER,

PS_LEDGER_BUDG

Alone Ledger tables All data

GL_JRNL_COPY

Copy PS_JRNL_HEADER,

PS_JRNL_LN,

PS_JRNL_VAT,

PS_OPEN_ITEM_GL

Anytime None

GL_SJE Create standardjournal entries

PS_JRNL_HEADER

PS_JRNL_LN

Anytime None None issued

FIN9001 Update PS recordsystem table

PS field systemtable

Prompt tables

Alone PeopleSoftApplicationDesigner

COMBO_BUILD_REQ

Build combodata

COMBO_DATA_TBL andselector tables(depending onthe setup)

Alone COMBO_DATA_TBL andselector tables(depending onthe setup)



The two processes GLS9001 and FIN9001 have names similar to reports, but these are processes.Because reports only perform Select access against the database, reports do not cause table or rowlocking, and they do not change data. Consequently, reports do not encounter concurrency issues. Butthese two processes, which are named like reports, have restrictions. FIN9001 must be run alone, andGLS9001 cannot be run concurrently with PeopleSoft Tree Manager and PS/nVision.

GLS9001.SQR

This utility performs Updates, Inserts, and Deletes against PeopleSoft system tree tables to load treeinformation from a flat file. You can also use the PeopleTools Tree Import utility as another method tomaintain trees from an external source. A commit is issued after all the data in the file has been loaded.You should not run online processes that use PeopleSoft Tree Manager or PS/nVision concurrently withthis utility because it holds a lock on the tree system tables until its completion.

SeePeopleTools Tree Manager PeopleBook: “Using Tree Mover”

FIN9001.SQR

This utility performs updates on information in both the PeopleSoft record and field system tables.Security implementation should ordinarily be a one-time activity during system configuration. Run thisutility by itself, because it modifies prompt tables and locks tables referenced by PeopleSoft ApplicationDesigner. The total start-to-finish time of this report is normally less than five minutes.

Background Process ConcurrencyThis section discusses the relationship between tables that each process uses and the effects the process can haveon concurrent activity within PeopleSoft General Ledger. This refers to runningdifferentprocesses concurrently.

The online process definition and request pages for each process control the actual data accessedfrom the following process information. The Allocations process, the Combination Edit process,the Journal Ledger process, and the Summary Ledger process are all Application Engine processes.The processes are presented here in alphabetical order by process name.

Allocations Application Engine Process (FS_ALLC)

The Allocations process references this functional data: record and field definitions, calendardata, allocation definitions, ledger information, tree definitions, timespans, and ChartField tablevalues. SELECT SQL access is used to retrieve this data.

Work tables ALC_xxx_TAO and TSEL_xxx_TAO are used to process the allocation calculations.Multiple INSERTS and UPDATES are performed against these tables within the unit of work interval.These tables are solely for the use of the Allocations background process.

The result of an allocation is the updating of ledger rows, the creation of journal entries, or both. INSERTand UPDATE activity required for these outputs occurs against the JRNL_HEADER, JRNL_LN, andLEDGER tables. The unit of work for an allocation is the allocation step.

Note. PeopleSoft General Ledger supports multiple journal and ledger tables. General Ledger tableallocation enables UPDATES and INSERTS to specified target and offset tables.



It is important to evaluate the time required to complete an allocation step. This is based on thefunctional requirements and the size of the basis, pool, and target for a given step. The estimatedtime to complete the unit of work determines the impact that allocation journal entry creation andledger update activity has on other concurrently running processes.

You can request that a calculation log be generated when an allocation step is processed in the background.This results in INSERTS being performed against the ALLOC_CALC_LOG table. The Structured QueryReport (SQR) that generates a report of the allocations calculation log, GLS6002.SQR, selects againstthis table. Therefore, you should not run the SQR GLS6002.SQR concurrently with the Allocationsbackground process if the steps being processed generate a calculation log.

Alternate Account Edit Application Engine Process (GL_AA_EDIT)

The Alternate Account Edit process is an Application Engine process that updates the records you specifyin the Combo Edit Template Line Record field and Line Error Log field. The Line Error Log record only isupdated if you set the ERRORHANDLER flag to true. (You must pass this field with a value ofY.)

The only system table that is used for transaction set editing is PSRECFIELD. This is onlyaccessed if the ERRORHANDLER flag is true.

Application tables used for SELECT SQL or editing are:

• PS_INSTALLATION

• PS_COMBO_EDIT_TMPL

• PS_BUS_UNIT_TBL_GL

• PS_COMBO_EDIT_LNS

• PS_LED_GRP_LED_TBL

• PS_LED_FLDS_TBL

• PS_BU_LED_GRP_TBL

• PS_ALTACCT_XREF

Average Daily Balance Calculation Process (GL_ADB_CALCX)

The Average Daily Balance process uses information from record and field definitions, average dailybalance (ADB) definitions, ledger definitions, calendar data, tree definitions, and the average dailybalance request record. SELECT SQL access is used to retrieve this data.

Work tables ADB_WTA_TAOnnnand LED_ADB_TAOnnnare used to process temporary data. Treeselector tables ADB_TREE_SELnnnare used to populate ChartField values from tree definitions. MultipleINSERTS and UPDATES are performed against these tables within the unit of work interval.

The main activity of the Average Daily Balance process is calculating average balances from the ADB ledgerof the specified period. The calculation results are inserted into the ADB target ledger table. The AverageDaily Balance process supports two different methods of calculating the averages: ad hoc and incremental.

With thead hocmethod, the process extracts the data from the ADB ledger to calculate the average balances.Run the Average Daily Balance process any number of times. The process deletes any previously calculatedaverage balances of the same period before it recalculates the new average balances.



With the incrementalmethod, the process uses the prior period averages and the data from the ADBledger. The process extracts only the data from the ADB ledger that is necessary to calculate the averagebalances. This would include any transactions that are posted between the prior and current requestedperiod. The process automatically applies adjustments to prior period averages. Run the Average DailyBalance process any number of times. The process uses an activity log table to determine the requiredprocessing. If the averages were already calculated for a given period, only the adjustments are applied.The process also used a date-time stamp on the log table to ensure that the adjustments are not appliedmore than once. This enables you to adjust averages as many times as needed.

The request record of the Average Daily Balance process enables you to specify multiple periods ofaverage balances to calculate, so that the commit point is a subset of the request record. A commit isissued after each period for which average balances are calculated and adjusted.

ChartField Combination Build Process (FS_CEBD)

The ChartField Combination Build process references the following data: record and field definitionsas defined on the combination template, combination rule and group definitions, tree definitions, andChartField table values SELECT SQL access is used to retrieve this data.

The result of the ChartField Combination Build process is a refresh of the valid ChartField combinationsin the PS_COMBO_DATA_TBL or the COMBO_SEL_nn selector tables.

The ChartField Combination Build background process uses these tables:

ChartField Combination Table Usage

COMBO_DATA_TBL Stores all the valid or invalid ChartField combinations(based on definition) as maintained by the CombinationBuild process (FSPECBLD).

SQL Selects are done against this to determine whichcombinations are defined by the combination rule.

COMBO_SEL_nn

(nn is a number between 01 and 30)

Stores the ranges of tree values used by the combinationrules for reference during core processing.

SQL Selects are done against these to determine whichcombinations are defined by the combination rule.

COMB_Snn_TAO

(nn is a number between 01 and 30)

Stores the ranges of tree values used by the combinationrules for reference during core processing.

These temporary combination selector tables are builtdynamically when the build process runs.

COMB_EXP_TAO If you use the combination selector table option,these tables are used to explode the tree ranges inCOMBO_SEL_nn into detail ChartField values. Whenfully expanded, these tables are joined with accountinglines for editing.



ChartField Combination Editing Process (FS_CEDT_PROC)

The ChartField Combination Editing process references the same functional data, as does the ChartFieldCombination Build process in the previous section. Likewise, SELECT SQL access is used to retrieve this data.

To enhance the performance of the editing, you can build the COMBO_SEL_nn masterselector tables before using the Combination Edit process.

Alternatively, you might decide not to build the selector tables. This causes the editingprocess to build them dynamically at the time of the edit.

If you prefer to edit directly against the COMBO_DATA_TBL without using the selector tablesat all, you can do so by indicating this on the Combo Group definition. On the Combo Groupdefinition, there is an Editing Option for indicating whether the COMBO_DATA_TBL or the selectortables can be used. However, if the COMBO_DATA_TBL is chosen as the editing option, thebatch editing does not dynamically build the COMBO_DATA_TBL. In this case, you must run theCombination Build process to create the combinations before the edit.

The background processing performs several updates to the accounting line tables defined in theCombination Template definition. Set processing logic is used to determine the validity of theChartField combinations. The result of ChartField combination editing is the updating of accountinglines with the statusInvalid if ChartField combination errors are found.

Closing Process (GLPCLOSE)

The Closing process uses information defined for record and field definitions, account types, accountattributes, calendars, ChartField value sets, ledger definitions, and closing rule definitions. It also uses ledgerand journals data to perform the closing. SELECT SQL access is used to retrieve this data.

The primary activity of the Closing process is to create closing ledger entries and journal entries foryear-end close, or closing journal entries for interim close. (Creation of journal entries to maintain anaudit trail is optional for year-end close; interim closealwayscreates journals.) The Closing process usesINSERT, UPDATE, and DELETE activity against the CLO_LEDG_TMPnnn, CLO_EARN_TMPnnn,CLO_ACCT_TMPnnn, CLO_JNHD_TMPnnn, CLO_JNLN_TMPnnn, CLO_JLN2_TMPnnn, CFV_SELnnn,CLO_ABG_TMP, LEDGER, JRNL_HEADER, and JRNL_LN tables. The unit of work for the Closingprocess is the same as the request itself—the closing of the ledger specified on the request. The closingprocess locks activity on the LEDGER table on accounting period 999 and 0, as well as JRNL_HEADER andJRNL_LN if journals are to be created. Consider this when planning activities that might be run concurrentlywith closing. In the event that processing is interrupted, periodic commits occur for a large volume of rows.

Additionally, if the close to multiple retained earnings option is activated, processing time dependsheavily on the ChartField value set definitions. Generally, the fewer ChartFields processed, the moreefficient the processing. On the other hand, it takes less time if there are fewer ChartField combinationsamong the ChartField value sets included in the closing rule definition.

Note. When processing interim close, the journals for the specified period are locked. Youshould not run other activities that require access to these journals.



Commitment Control Budget Closing Process (FSPYCLOS)

The LEDGER_KK table, which holds the Commitment Control budget balances, is selected andupdated during the Budget Closing process. Calculation log entries in tables KK_CLOSE_CALC_S,KK_CLOSE_CALC_T, and KK_CLOSE_OFFSET are created to provide the supporting informationon how the remaining balances are updated and rolled forward to a new budget period. One ormore rows are created for the process log table KK_CLOSE_PR_LOG, which can be reviewedonline and undoes the Budget Close process. KK_BD_ATTRB_MST, KK_BD_ATTRIB, andKK_BD_ATTRIB_BP are updated for the budget status. INSERTS and UPDATES are performedagainst this table within the unit of work interval. KK_CLOSE_STATUS is maintained by both theBudget Closing process and the Run Control Validation process (GLS1211) to track the closing statusof Budget Ledgers by Budget Period, and it can be reported or reviewed online.

The Budget Closing process creates Commitment Control journals in KK_BUDGET_HDR and KK_BUDGET_LN tables, and it calls the Budget Journal Posting process (FSPQPOST) to update the LEDGER_KK table.

Work tables KK_BD_ATTRB_TMP and KK_RSCFV_SEL are used for updating the Budget Status tables;selector tables CFV_SELnnnare used when querying ledger balances during the process. Multiple INSERTS,UPDATES, and DELETES are performed against these tables within the unit of work interval.

Commitment Control Budget Post Process (FSPQPOST)

The Commitment Control Budget Post process edits, posts, and budget-checks the Commitment Control budgetjournals. It accesses various Commitment Control definition tables and PeopleSoft record definition tables.

The process uses work tables KK_BDHDR_TMPnnn, KK_BD_LN_TMPnnn, KK_LEDG_TMPnnn, andKK_LEDG_TMP2nnn to store temporary budget header, line, and ledger balances.

The process issues a commit after the editing is done. Next, it posts and budget-checks the journal.Finally, it issues another commit. The unit of work is an individual journal.

Commitment Control Budget Process (FSPKBDP3)

Background budget processing updates the Commitment Control ledger, activity, source transaction,liquidation, log and exception tables, as well as various application header and line tables as definedin the Commitment Control Source Transaction Definition component. It also accesses variousCommitment Control definition tables and PeopleSoft record definition tables.

The Commitment Control Budget process also updates these Commitment Control tables:

• PS_KK_SOURCE_HDR

• PS_KK_SOURCE_LN

• PS_KK_ACTIVITY_LOG

• PS_LEDGER_KK

• PS_LIQUIDATION

• PS_KK_REFERENCED

• PS_KK_TRANS_LOG

• PS_KK_EXCPTN_TBL

• PS_KK_CHECK_REQ



• PS_KK_CHECK_REQ2

The process accesses these Commitment Control tables:

• PS_KK_BUDGET_TYPE

• PS_KK_SUB_TYPE

• PS_KK_KEY_CF

• PS_KK_CF_VALUE

• PS_KK_EX_ACCT_TYPE

• PS_KK_EX_ACCT_VAL

• PS_KK_BD_DFLT_ACCT

• PS_KK_BD_OFFSET

• PS_KK_TRX_OFFSET

• PS_KK_BD_ATTRIB

• PS_KK_BD_ATTRIB_BP

• PS_KK_REV_XREF

• PS_KK_EX_XREF

• PS_KK_FS_VALUE

• PS_KK_SOURCE_TRAN

• PS_KK_TRAN_SELECT

• PS_KK_STATUS_FLDS

• PS_KK_REFREC_KEYS

The process accesses these application definitional tables:


• PS_BUL_CNTL_BUD

• PS_LED_GRP_TBL

• PS_LED_FLDS_TBL

• PS_CAL_DETP_TBL

• PS_CAL_BP_TBL

• PS_GL_ACCOUNT_TBL

The process accesses these PeopleTools definitional tables:

• PSDBFIELD

• PSRECFIELD

Depending on the product calling Budget Processor, the Commitment Control budget process accesses certainapplication records and updates their status flags. The source tables from which data is selected are:

• PS_VCHR_ACT_HDR_VW



• PS_VCHR_ACT_LN_VW

• PS_VCHR_HDR_NP_VW

• PS_DIST_LINE_NP_VW

• PS_VOUCHER

• PS_DISTRIB_LINE

• PS_ARCC_PAY_HDR_VW

• PS_ARCC_PAY_DTL_VW

• PS_AR_CC_TRAN_VW

• PS_AR_CC_TRAN_TBL

• PS_BI_ACCT_KK_VW

• PS_BI_ACCT_KK2_VW

• PS_CM_KK_HDR_VW

• PS_CM_KK_LINE_VW

• PS_EX_SHEET_HDR

• PS_EX_SHEET_DIST

• PS_EX_TAUTH_HDR

• PS_EX_TAUTH_DIST

• PS_COMCNTL_TRN_HDR

• PS_COMCNTL_TRN_LN

• PS_JRNL_HEADER

• PS_JRNL_LN

• PS_GM_PRJ_RHDR_VW

• PS_GM_PRJ_RES_VW

• PS_HR_KK_HDR

• PS_HR_KK_LN_VW

• PS_INTFC_PC_KK_VW

• PS_INTFC_PC_LN_VW

• PS_PO_HDR

• PS_PO_LN_DIST_KK

• PS_PO_HDR_NP

• PS_PO_LN_DST_NP_KK

• PS_CC_TRANS_LINE

• PS_CC_TRANS_DIST

• PS_RECV_ENC_HDR_VW



• PS_RECV_ENC_LN_VW

• PS_RECV_EXP_HDR_VW

• PS_RECV_EXP_LN_VW

• PS_REQ_HDR

• PS_REQ_LN_DISTRIB

The following source tables are updated:

• PS_VCHR_ACCTG_LINE

• PS_VOUCHER

• PS_DISTRIB_LINE

• PS_VCHR_HDR_NP_VW

• PS_DISTRIB_LINE_NP

• PS_PAYMENT

• PS_PAY_MISC_DST

• PS_AR_CC_TRAN_HDR

• PS_AR_CC_TRAN_TBL

• PS_BI_ACCT_ENTRY

• PS_BI_ACCT_KK2_VW

• PS_CM_ACCTG_LINE

• PS_EX_SHEET_HDR

• PS_EX_SHEET_DIST

• PS_EX_TAUTH_HDR

• PS_EX_TAUTH_DIST

• PS_COMCNTL_TRN_HDR

• PS_COMCNTL_TRN_LN

• PS_JRNL_HEADER

• PS_JRNL_LN

• PS_GM_PRJ_RHDR_VW

• PS_GM_PRJ_RES_VW

• PS_HR_KK_HDR

• PS_HR_ACCTG_LINE

• PS_INTFC_PC_LN_VW

• PS_PO_HDR

• PS_PO_LINE_DISTRIB

• PS_PO_HDR_NP



• PS_PO_LINE_DIST_NP

• PS_CC_TRANS_LINE

• PS_CC_TRANS_DIST

• PS_REQ_HDR

• PS_REQ_LN_DISTRIB

• PS_ RECV_LN_ACCTG

Volume estimates depend on the database platform used. Narrow the request level criteria tolower the volume of transactions processed in a unit of work.

Consolidations Process (GLPOCONS)

The Consolidations process uses this functional information: tree definitions, calendar data,elimination sets, minority interest sets, ledger information, and ChartField table values.SELECT SQL access is used to retrieve this data.

Work tables CONSOL_SEL_TBL, CONSOL_SEL2_TBL, and CONSOL_SEL3_TBL are used toprocess tree definition data; CONSOL_EQTY_TMP is used in calculating minority-interest-relatedelimination. CONSOL_STAT_TMP is used to hold the process status at tree node level. Selector tablesCFV_SELnnn are used when querying ledger balances during the process. CONSOL_ENT_TMP isused to hold the overflowed (from COBOL array) consolidation entity—for example, business unitinformation during the process. CONSOL_BAL_TMP is used to hold balances by balancing ChartFieldswithin a journal to ensure the journals created are balanced. Multiple INSERTS, UPDATES, andDELETES are performed against these tables within the unit of work interval.

The primary INSERT, UPDATE, and DELETE activity against multiple use tables occurs when generatingelimination entries for consolidations. Inserting rows into the JRNL_HEADER and JRNL_LN tables createsjournal entries. The Journal Edit (GL_JEDIT) process and the Journal Post (GLPPPOST) process are calledto edit and post the journals. Please refer to those sections for details on tables accessed.

The request record for the Consolidations process enables you to review elimination results by runningthe process in Log mode. In this mode, the Consolidations process performs all the calculations necessaryto generate consolidated results and stores that information in the CONSOL_LOG table. Run theConsolidations process any number of times until you have resolved all discrepancies. Once you obtain thedesired results, run the process a final time to actually generate the elimination journal entries. Potentiallocking problems are not applicable while in Log mode. One row is inserted into the process log table,CONSOL_PROC_LOG, which can be reviewed online. You use it to undo the Consolidation process.

The Consolidation process also maintains the process status in CONSOL_ND_STAT. Thestatus appears on the Consolidation Process Monitor page.

Equitization Process (GLPQEQTZ)

The Equitization process is similar to the Consolidation process with regard to tables that are used or affected.

Work tables CONSOL_SEL_TBL, CONSOL_SEL2_TBL, and CONSOL_SEL3_TBL are used toprocess tree definition data; EQTZ_POOL_TMP is used to hold the interim calculation results;and selector tables CFV_SELnnn are used when querying ledger balances during the process.CONSOL_ENT_TMP is used to hold the overflowed (from COBOL array) consolidation entity—forexample, business unit—information during the process. Multiple INSERTS, UPDATES, andDELETES are performed against these tables within the unit of work interval.



The primary INSERT, UPDATE, and DELETE activity against multiple-use tables occurs when generatingequitization entries. Inserting rows into the JRNL_HEADER and JRNL_LN tables creates journalentries. The Journal Edit (GL_JEDIT) process and the Journal Post (GLPPPOST) process are calledto edit and post the journals. Refer to those sections for details on tables accessed.

These activities occur within the Equitization process unit of work interval, which is the same as the request. Itis important to evaluate the size of equitization source and the expected number of journal entries to be createdto estimate the unit of work interval. If the interval is short, there should be little impact on other parts of thesystem that enable journal entry creation or ledger updating. If the interval of the unit of work is long, then youshould avoid other journal entry creation and ledger updating activity when creating equitization journal entries.

The request record for equitization enables you to review equitization results by creating thecalculation log and store that information in the EQTZ_CALC_LOG table. Unlike the Consolidationprocess, the Equitization process does not have a Calculation Log Only mode. The calculationlog is a side-product for each successful equitization run.

One entry to EQTZ_PROC_LOG is also created to retain the request information for the Undo process. TheUndo option in the equitization request causes the process to delete the entry from last process request.

Flat File Journal Import Process (GL_JRNL_IMP)

This import process interfaces with third-party systems that produce flat files containing journal entries.

This process inserts rows into the journal tables from data in a flat file. A commit is used after all data in the file isloaded. You can separate journal data into smaller flat files and run several instances of this process concurrently.

Flat File Ledger Import Process (GL_LED_IMP)

This import process interfaces with third-party systems that produce flat files containing ledger entries.

This process inserts rows into the PS_LEDGER and PS_LEDGER_BUDG tables from data in aflat file. A commit is issued after all the data in the file is loaded.

You should run this process by itself because it locks ledger tables until it terminates.

HRMS Account Code Interface Process (HR_ACCT_CD)

This process reads information and sends it out as a message to another user ID. When theHRMS Account Code Interface (Human Resources Management account code interface) process(HR_ACCT_CD) runs, no contention for system tables occurs.

This process runs the Build Combination Data process and then the HRMS/SA extract ApplicationEngine process. The latter extracts data out of the combo data table and sends it to the Human Resourcessubsystem using PeopleSoft Application Messaging. Because this process also runs the Build CombinationData process, do not run HR_ACCT_CD concurrently with any other background process that use thecombination data table, the selector tables or the exploded combination table.

Journal Copy Application Engine Process (GL_JRNL_COPY)

This Application Engine process copies journal line information to a new journal. Thereshould not be any concurrency issues with this process.



Journal Edit Process (GL_JEDIT)

Background journal editing updates the journal header, journal line, journal value-added tax (VAT),InterUnit and IntraUnit journal anchor, journal totals, TSE journal header log, and TSE journal line logtables. It also accesses various tools (PeopleSoft Application Designer for record definition), systemdefinition tables, ChartField tables, and ChartField combination data and rules tables.

The system tables used for transaction set editing are PSDBFIELD, PSRECDEFN, and PSRECFIELD.

Other tables used to edit individual journals are:


• PS_BU_LED_TBL


• PS_CAL_DEFN_TBL

• PS_CAL_DETP_TBL

• PS_RT_TYPE_TBL

• PS_LED_DEFN_TBL

• PS_OPEN_ITEM_GL

• PS_GL_POS_ACT_DEF

• PS_GL_POS_ACT_CFS

• PS_GL_POS_ACT_DETL

• PS_SET_CNTROL_REC

• PS_SET_CNTROL_TBL

• PS_SET_CNTROL_TREE

• PS_SOURCE_TBL

• XLATTABLE

• Various ChartField tables

• Various VAT definition tables

Tables that are updated during background journal edits are the following:

• PS_JRNL_EDIT_REQ

• PS_JRNL_EDIT_LOG

• PS_JRNL_HEADER

• PS_JRNL_LN

• PS_JRNL_CF_BAL_TBL

• PS_TSE_JHDR_FLD

• PS_TSE_JLNE_FLD

• PS_JRNL_VAT



• PS_JRNL_IU_ANCHOR

Work tables that are used during background journal edits for storing temporary data are:

• PS_BK_ALL_TAO

• PS_BK_CLSE_TAO

• PS_BK_OPEN_TAO

• PS_JLN_SUS_TAO

• PS_JLN_VATC_TAO

• PS_JRNL_IUWK_TAO

• PS_JRNL_LN_TAO

• PS_LED_TMPLT_TAO

• PS_VAT_IU_GL_TAO

• PS_VAT_IU_PR_TAO

The Journal Edit process uses application locking instead of database locking to lock the journals beingedited. When the Journal Edit process starts, it updates the journal header’s JOURNAL_LOCKED field toYto set the application locking. While the journals are locked, they cannot be used by other online or batchactivities. After each journal is edited, its JOURNAL_LOCKED field is reset to blank and a commit isissued. Consequently, the journal is unlocked. The request record for journal edit processing enables youto specify a range of journals to edit, so that the commit point is a subset of the request level.

It is important to evaluate the size of the background Journal Edit process run for a specific request. The sizedetermines whether or not concurrent activity is successful against the journal tables. Performance timingsof the Journal Edit process indicate that a medium volume of journals should be an acceptable level forconcurrent activity. Avoid large volumes when other journal processing activity needs to occur.

Volume estimates also depend on the database platform used. Narrow the request level criteria to lowerthe volume of journals processed in a unit of work. Process large journals as separate requests.

Journal Generator Process (FS_JGEN)

The Journal Generator process uses information from record and field definitions, accounting entry definitions,journal generator template, General Ledger business unit, ledger definitions, calendar data, journal sources,tree definitions, and the journal generator request record. SELECT SQL access is used to retrieve this data.

Work tables JGEN_WRK_TMP are used to create journals from accounting entries. Tree selectortables JGEN_TRnnSel are used to populate ChartField values from tree definitions. MultipleINSERTS and UPDATES are performed against these tables within the unit of work interval. Thesetables are solely for the use of the Journal Generator background process.

The main activity of Journal Generator is creating journal entries from accounting entries. Journalentries are created in two steps. The first step inserts rows into the JGEN_WRK_TBLnnnwork tablefrom accounting entries. The second step inserts rows into the JRNL_HEADER and JRNL_LN tablesby selecting from the JGEN_WRK_TBLnnnwork table. The accounting entries are then updatedwith the journal information. A commit is issued after each journal is created.



Journal Post Process (GLPPPOST)

The Journal Post process references data from the record and field definitions, ledger definitions, andthe journal request record. SELECT SQL access is used to retrieve this data.

Posting has two primary functions:

1. To UPDATE or INSERT rows into the LEDGER table to which you are posting. Rows inJRNL_HEADER are updated after they are successfully posted.

2. To create journal entries for the unpost and reversal creation process. This consists of UPDATE, INSERT,and DELETE activity against the JRNL_HEADER and JRNL_LN tables. The posting unit of work isthe same as the request. If open item journals are involved, table OPEN_ITEM_GL is updated.

Work tables LEDGER_TMPnnn, LEDGER_TMP2nnn, JRNL_HDR_TMPnnn, JRNL_HDR_SELnnn,JRNL_LN_TMPnnn, and GL_OI_TMPnnnare used to process journal posting. GL_OI_TMPnnn is used ifthe Open Item Reconciliation process runs. JRNL_XRF_TMPnnn is used if suspense correction journalsare involved. JRNL_VAT_TMPnnn is used if VAT-related journals are processed. Multiple INSERTSand UPDATES are performed against these tables within the unit of work interval.

Based on the request options or the configuration of the ledgers, additional tables may be updatedduring the posting process. OPEN_ITEM_GL is updated if the Open Item Reconciliation processis selected. LEDGER_ADB_HLD is updated if an average daily balance is maintained for thisledger. SLEDGER_STG is updated if incremental summary ledger is enabled. LED_LOAD_STGis updated if incremental ledger load option is enabled.

Success or failure of concurrent activity depends on whether the two processes attempt to update orinsert the same ledger rows. The Posting process can run concurrently if the data sets are mutuallyexclusive (by business unit, ledger, year, period, or ChartField values).

Avoid large volumes when other journal and ledger process activity needs to take place.

Volume estimates also depend on the database platform used. Narrow the request level criteria to lowerthe volume of journals processed in a unit of work. Process large journals as separate requests.

Ledger Load Process (GL_LED_LOAD)

The Ledger Load process updates the ledger table, a staging table for incremental ledger load and ledgerload log tables. It also accesses various system definition tables and ChartField mapping tables.

The system table PSRECFIELD is used for checking whether the database is set up for separate debits and credits.

Other tables used to edit individual journal are:


• PS_CAL_DETP_TBL

• PS_CF_MAPPING_SET

• PS_CF_VALUE_MAP

• PS_CFV_MAP_BU_SET

• PS_CF_TARGET_TBL

• PS_CF_SOURCE_TBL

• PS_CF_MAPPING_CF



• PS_LED_TMPLT_TBL


• PS_LED_GRP_LED_TBL

Tables that are updated during the Ledger Load process are PS_LEDGER, PS_LOAD_LEDGER_TMP and PS_LED_LOAD_LOG.

The Ledger Load process updates the ledger table. Evaluate the size of the run for a specificrequest. Because the process locks the rows in the ledger table for the specific run, avoidlarge volumes when other ledger activities need to occur.

Multicurrency Processing Process (FSPCCURR)

The Multicurrency Processing process references the following functional data: record and field definitions,account attributes, calendar data, translation and revaluation definitions, ledger information, tree definitions,timespans, and ChartField table values. SELECT SQL access is used to retrieve this data.

Background multicurrency processing uses the CURR_WRK_TBLnnn, CUR_WRK1_TBLnnn, andTREE_SELnn_Rnnnwork tables. Multiple INSERTS and UPDATES are performed against these tableswithin the unit of work interval. These tables are solely for the use of background multicurrency processing.

The result of multicurrency processing is the updating of ledger rows and the creation of journalentries. INSERT and UPDATE activity required for these outputs occurs against the JRNL_HEADERJRNL_LN tables. The unit of work for multicurrency processing is a revaluation or translation step.Note that PeopleSoft General Ledger also supports multiple journal and ledger tables for various ledgertemplates. The temporary table names are different across ledger templates.

Evaluate the time required to complete a multicurrency step. This is based on the functional requirementsand the number of ChartKeys that are restated as defined in the revaluation step or translation rulesin a step. The estimated time to complete the unit of work determines the impact that journal entrycreation and ledger update activity has on other concurrently running processes.

Open Item Reconciliation Process (GLPPOITM)

The only table that Open Item Reconciliation updates is the OPEN_ITEM_GL table. The unit of workis the same as the request. Work table GL_OI_TMPnnn is used for the Open Item Reconciliation process.INSERTS and UPDATES are performed against this table within the unit of work interval.

Post Daily Balance Process (GL_ADB_POST)

The Post Daily Balance process uses the following information to post the journal transactions to the ADBledger: business unit and ledger data, calendar data, ledger template, and the posted activity from the JournalPost process (contained in a holding table). SELECT SQL access is used to retrieve this data.

Work tables LED_ADB_TAOnnn, LED_ADB_TAO2nnn, and LED_ADB_TAO3nnn areused to post balances to the ADB ledger. Multiple INSERTS and UPDATES are performedagainst these tables within the unit of work interval.

The main function of the Post Daily Balance process is to post the daily balances to the ADB ledger from theADB ledger holding table. The ADB ledger holding table contains posted journal activity from the Journal Postprocess. To ensure the accuracy of the balances, the Post Daily Balance process deletes the posted activity fromADB ledger holding table after it is posted to the ADB ledger. The Post Daily Balance process also inserts datainto the ADB adjustment holding tables for posted activity that is required to adjust average daily balances.



All temporary and holding tables, including the ADB ledger, are defined in the ledgertemplate page under the ADB record names group.

A commit is done after the balances are posted and the data is cleared from the adjustment holding table.The time to complete this step is determined by the number of transactions that are posted.

Summary Ledger Application Engine Process (GL_SUML)

The Summary Ledger process uses information from tree definitions, calendar data, and ledger definitionsfor both summary and detail ledgers. SELECT SQL access is used to retrieve this data.

Multiple INSERTS, UPDATES, and DELETES are performed on the summary ledger table,S_LEDGER_xxxxxx, and on the status table, SUMLED_STATUS. The incremental summary ledgerupdate also updates and deletes rows from the staging table, SLEDGER_STG.

SUMLED_SEL_nn work tables are used to process tree definition data. Multiple INSERTS andDELETES are performed against these tables and the S_xxxxxx_TMP table within the unit ofwork interval. Only the summary ledger process uses these tables.

The main activity of the Summary Ledger process is inserting data into the summary ledger defined on therequest. The INSERT is accomplished with one SQL statement, comprising one unit of work. A commit isissued after each summary ledger is created. The request record for summary ledger processing enablesyou to specify a range of summary ledgers to create, so that the commit point is a subset of the requestlevel. No concurrency problems have been identified within the Summary Ledger process.

Warning! The incremental Summary Ledger process should not be run concurrently for any single businessunit and summary ledger combination. If multiple posting instances run concurrently and call the SummaryLedger process (for the same ledger and business unit combination), bad results or collisions can occur.

Spreadsheet Journal Batch Import Process (GL_EXCL_JRNL)

This process inserts rows into the journal tables from data contained in a flat file that youcreate using the PeopleSoft General Ledger Spreadsheet Journal Import utility. A commitis used after all data in the file has been loaded.

You can separate the journal data into smaller flat files and run several instances of this process concurrently.

Standard Journal Entry Application Engine Process (GL_SJE)

This Application Engine process creates standard journal entries. There should not beany concurrency issues with this process.

See Also


Chapter 8, “Making General Ledger Journal Entries,” page 107


CHAPTER 6

Integrating and Transferring InformationAmong Applications

This chapter provides an overview of the PeopleSoft Financials General Ledger EnterpriseIntegration Points, Flat File Import processes and discusses how to:

• Create journals from accounting entries using journal generator.

• Integrate PeopleSoft General Ledger with PeopleSoft Applications.

• Integrate PeopleSoft General Ledger with PeopleSoft Enterprise Management Budgeting.

• Import journal entries.

• Transfer ledgers for consolidation.

Understanding Enterprise Integration Points (EIP)in PeopleSoft General Ledger

PeopleSoft General Ledger is often the repository of your accounting information. It receives datafrom other PeopleSoft applications, such as PeopleSoft Accounts Payable, Project Costing, HCMPayroll, Learning Solutions, and Enterprise Learning Management, as well as third-party applications.These are referred to as feeder or subsystem applications. You can also load data such as journaland ledger file imports directly into General Ledger. General Ledger can also export data, suchas ledgers, and publish and subscribe data for global consolidation.

In additional to flat file imports, the General Ledger interface uses Enterprise Integration Points (EIPs),also known as data publish and subscribe, across applications. EIPs simplify cross-product integration andautomate data transport by providing a pre-defined structure of the data message among involved parties

This diagram displays how transactions are imported and processed in General Ledger:


Integrating and Transferring Information Among Applications Chapter 6

PeopleSoft GLSpreadsheet

JournalExternalSystem

SpreadsheetJournal Import

Flat FileJournal Import

Journals

JournalGenerator

Posting

AccountingTables

StandardDetail

Ledger

Genericaccounting

entry

HCM, LS, ELMaccounting

entry

A

StandardBudgetLedger

LEDGER_BUDG_KK

CommitmentControl

Journals

CommitmentControl BudgetJournal Import

AllocationCommitment

Control Posting

CommitmentControl LedgerSummary

Ledger

Ledger Load(ChartField

value mapping)LedgerPublish

Flat FileLedger Import

PeopleSoft GL(regional)

ExternalSystem

ExternalSystem

Commitment ControlBudget Update

Ledgerinterface

PeopleSoftGeneral Ledger

ExternalSystem

North America Payroll,Global Payroll,

Learning Solutions,Enterprise Learning

Management

HCM North America Payroll

EPM Budgeting

ETLUtility

A

ChartField

BusinessUnit

LedgerDefinition

XBRLDocument

SpeedType

JournalGeneratorTemplate

ComboData Table

Calendar

Combo EditRequest/

Reply

Budget CheckTransaction

BudgetProcessor

ExternalSystem

PeopleSoft General Ledger Integration diagram

See Also

PeopleTools PeopleBook: PeopleSoft Integration Broker

PeopleSoft Enterprise Components PeopleBook: “PeopleSoft Enterprise Integration”


Chapter 6 Integrating and Transferring Information Among Applications

PrerequisitesSeveral General Ledger file import processes allow you to submit the file from the web page and then runthe import processes on a batch server. There are one time setups that you must perform to prepare yoursystem for these tasks. These file import processes depend on the setup described in this table:

Process Process Object Name

Flat file journal import GL_JRNL_IMP

Flat file ledger import GL_LED_IMP

Spreadsheet journal batch import GL_EXCL_JRNL

Commitment Control budget journal import KK_JRNL_IMP

FACTS II Load MAF data GL_F2_MAF

The storage location of the file attachment is defined by the URL definition GL_FILE_IMPORT. Bydefault, it points to a database record. You may want to change the storage location of the file attachmentto another location, such as an FTP server. This is optional. Please refer to the “File AttachmentArchitecture” PeopleBook for more details. To change this URL definition, navigate to:

PeopleTools, Utilities, Administrations, URLs, open GL_FILE_IMPORT

You are required to define an environmental variable, PS_FILEDIR. This variable defines thetemporary flat file location on the process scheduler that runs the file import process. If you havea Unix or OS390 process scheduler, you define this in the psconfig.sh file. If you have an NTprocess scheduler, you define this in the control panel. Please refer to the GetFile() PeopleCodereference for more details or contact your system administrator.

See Also

PeopleTools PeopleBook: PeopleCode Developer’s Guide:"Using Methods and Built-inFunctions," Understanding File Attachment Architecture

PeopleTools PeopleBook:” PeopleCode Reference,” File Class, File Class Built-in Functions



Creating Journals from Accounting Entries UsingJournal Generator

While you can load data directly into the General Ledger tables, it is more common to postjournals to the General Ledger that are generated from a PeopleSoft application accountingentry table and from a generic accounting entry table, PS_JGEN_ACCTG_ENTRY, reserved forthird-party applications. The following sections discuss how to:

• Use Journal Generator with PeopleSoft applications.

• Use Journal Generator with third-party applications.

Using Journal Generator with PeopleSoft ApplicationsPeopleSoft feeder applications typically generate accounting or voucher lines from transaction datathat you enter in that particular application. PeopleSoft posts these accounting lines to an accountingentry table. Journal Generator processes data in the accounting entry table to create journals inGeneral Ledger and optionally edit and post them to the ledgers.

You can create journal entries and optionally post them from any of these PeopleSoft applications:

PeopleSoft Application Name PeopleSoft Application Name

Asset Management Promotion Management

Accounts Payable Purchasing

Accounts Receivable Treasury

Billing ELM — Enterprise Learning Management

Contracts Learning Solutions − Contributor Relations

Expenses Learning Solutions − Student Financials

Grants HCM — Global Payroll

Inventory HCM — North America Payroll

Project Costing

Note. ELM, HCM and Learning Solutions are PeopleSoft products running in a different databasefrom PeopleSoft General Ledger. Accounting entries from these products are transferred over EIPs(Enterprise Integration Points) and then processed by Journal Generator.



See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Using Journal Generator,” Understanding Journal Generator

Using Journal Generator with Third-Party ApplicationsWhen you create accounting entries in non-PeopleSoft third-party application systems, you can usethe Journal Generator to generate journal entries. This enables non-PeopleSoft applications to createjournals from each application’s business unit to different General Ledger business units, as well asto different ledger groups and ledgers for a General Ledger business unit.

You can use the Journal Generator to create journal entries from any table in a database as longas the table contains the required fields. If the field names are different but the attributes are thesame, you can create a view and point the Journal Generator to it.

You load your third-party transactions to a generic PeopleSoft accounting entry tablePS_JGEN_ACCTG_ENTRY for further processing by the Journal Generator. This table works the same as thePeopleSoft accounting entry table used by PeopleSoft applications. You can use this table for your third-partyapplications, or you can clone it and make changes to the original table and the cloned table.

PeopleSoft delivers the Accounting Entry EIP to populate your accounting entry table. The EIP providessample publish and subscribe code for you to clone and modify to meet your third-party journal generationrequirements. It uses PeopleCode subscribe on the subscription side. Since PeopleSoft does not determine apublisher, the publisher is normally third-party software that generates XML messages directly to the PeopleSoftsystem. Therefore, the publish code presented in the EIP serves as an example to illustrate the publishing logic.

General Ledger subscribes to the published message and populates the generic accounting entry tablePS_JGEN_ACCTG_ENTRY with the third-party transaction data. Once this table is populated, youuse the Journal Generator to create journal entries for the General Ledger.

The message and channel name is JOURNAL_LOAD_TEMPLATE, which uses the PeopleCodeSubscribe design pattern and the Message Subscription Name JournalLoadTemplate. Please seethe message subscription for sample publish and subscribe logic.

Note. PeopleSoft does not provide direct support to third party products, although PeopleSoft customersand third parties may use these EIPs as delivered or customize them based on their needs.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Using Journal Generator,” Understanding Journal Generator

Integrating PeopleSoft General Ledger withPeopleSoft Applications

In this section we describe how to:

• Activate integrations.



• Publish initial setup (fullsync) data.

• Publish incremental setup (sync) data.

• Use transactional and other messages.

PrerequisitesBefore you attempt to set up integration between PeopleSoft General Ledger and other PeopleSoftproduct applications that involve using EIPs, you must:

• If you are integrating with PeopleSoft HCM products, Select the HCM product in Set UpFinancials / Supply Chain, Install, Installation Options, Products page.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions,Enterprise Service Automation, and Supply Chain Management PeopleBook, “SettingInstallation Options for PeopleSoft Applications”.

• Read the Integration Broker Monitor chapter thoroughly.

SeePeopleTools PeopleBook: PeopleSoft Integration Broker, Using Integration Broker Monitor

• Review the Integration Broker chapters to learn how to set up and manage the IB Gateway.

SeePeopleTools PeopleBook: PeopleSoft Integration Broker

Activating IntegrationsFollow these basic steps to activate integrations on your database. You should perform the setup taskson both the publishing and subscribing databases, unless stated otherwise.

Setup task Navigation

Setup and configure Integration Broker Gateway

(There are multiple steps to setup the gateway. Please seePeopleTools PeopleBook for details)

PeopleTools, Integration Broker, Gateways.

Review permission to monitor messages PeopleTools, Security, Permissions and Roles, PermissionList, Message Monitor.

Activate Messages Application Designer, Message property.

Activate Message Subscriptions

(subscription database only)

Application Designer, Message subscription property.

Activate Message Channels Application Designer, Message channel property.

Alternatively, you can do this from PeopleTools,Integration Broker, Monitor, Channel Status.

Activate Node Definitions PeopleTools, Integration Broker, Node Definition.



Setup task Navigation

Define or activate Transactions

(Most EIPs are cross-node integrations, of which youdefine transactions on the remote node of each database)

For PeopleTools 8.4x select PeopleTools, IntegrationBroker, Node Definition, Transactions.

For PeopleTools 8.1x use Application Designer, Channel,Use tab, Pub/Sub node.

Define or activate Full Data Publish Rules

(Full data publish on publishing database only)

Enterprise Components, Integration Definitions, Full DataPublish Rules.

Activate any Integration Broker relationships PeopleTools, Integration Broker, Relationships

After you have setup your integration system, you are ready to use it by triggering EIPsaccording to your requirements and business events. Here is the list of setup and transactionalEIPs for use with PeopleSoft General Ledger:

Application Message Name Channel Direction Remarks

Setup Integrations:

ACCOUNT_CHARTFIELD_FULLSYNC

ACCOUNT_CHARTFIELD_SYNC

BUS_UNIT_GL_FULLSYNC

BUS_UNIT_GL_SYNC

LEDGER_DEFN_FULLSYNC

LEDGER_DEFN_SYNC

GL_SETUP Out Async

BUD_PERIOD_CALENDAR_FULLSYNC

BUD_PERIOD_CALENDAR_SYNC

DETAIL_CALENDAR_FULLSYNC

DETAIL_CALENDAR_SYNC

DETAIL_CALENDAR

Out Async

PROJECT_FULLSYNC

PROJECT_SYNC

PROJECT_STATUS_FULLSYNC

PROJECT_STATUS_SYNC

PROJECTS_SETUP Out Async




BUS_UNIT_AV_FULLSYNC

BUS_UNIT_AV_SYNC

BUS_UNIT_HR_FULLSYNC

BUS_UNIT_HR_SYNC

BUS_UNIT_SF_FULLSYNC

BUS_UNIT_SF_SYNC

HR_SETUP In Async

JOURNAL_GEN_APPL_ID_FULLSYNC

JOURNAL_GENERATOR_APPL_ID_SYNC

JOURNAL_GENERATOR

Out Async Journal GeneratorTemplate

DEPT_FULLSYNC

DEPT_SYNC

ENTERPRISE_SETUP

Bi-directional Async




BUS_UNIT_FS_FULLSYNC

BUS_UNIT_FS_SYNC

ALTACCT_CF_FULLSYNC

ALTACCT_CF_SYNC

BUDGET_REF_CF_FULLSYNC

BUDGET_REF_CF_SYNC

BUDGET_SCENARIO_FULLSYNC

BUDGET_SCENARIO_SYNC

CHARTFIELD1_FULLSYNC

CHARTFIELD1_SYNC


CHARTFIELD2_SYNC



CLASS_CF_FULLSYNC

CLASS_CF_SYNC

FUND_LOAD

FUND_CF_SYNC

OPER_UNIT_CF_FULLSYNC

OPER_UNIT_CF_SYNC

PRODUCT_CHARTFIELD_FULLSYNC

PRODUCT_CHARTFIELD_SYNC

PROGRAM_CF_FULLSYN

PROGRAM_CF_SYNC

ENTERPRISE_SETUP

Out Async

HR_ACCT_CD_LOAD ENTERPRISE_SETUP

Out Async Launch from theCombination Buildprocess request.

Replaced flat fileSQR interface in 8.0(GLCF001.SQR andBUD003.SQR)




HR_CHARTFLD_COMBO_SYNC HR_CHARTFLD_COMBO

Out Async Launch fromSpeedType page.

Transactional Integrations

PAYROLL_ACCTG_TRANSACTION

PAYROLL_ACCTG_TRANSACTION

Bi-directional Async HCM North AmericaPayroll

See Note #1

GP_POST_GL GP_POST_GL Bi-directional Async HCM Global Payroll

See Note #1

STUDENT_ADV_ACCTG_LINE

STUDENT_FIN_ACCTG_LINE

STUDENT_ADMIN_ACCOUNTING

Bi-directional Async Learning Solutions

See Note #1

LM_ACCTG_LN LM_ACCTG_ENTRY

Bi-directional Async ELS EnterpriseLearningManagement

See Note #1

JOURNAL_LOAD_TEMPLATE JOURNAL_LOAD_TEMPLATE

In Async Generic accountingentry for demo anduser’s customization.

COMMIT_CNTRL_BUDGET_UPDATE

COMMIT_CNTRL_BUDGET_UPDATE

In Async Commitment Controlbudget journals

COMMIT_CNTRL_TRAN_CHECK_UPDATE

COMMIT_CNTRL_TRAN_CHECK_UPDATE

Bi-directional Async Budget checking forcommitment controltransactions

LEDGER_LOAD LEDGER Bi-directional Async Works with theLedger Load processto move ledgerdata from regionalGL to headquarterGL database forconsolidation.




XBRL_ASYNC XBRL Out Async XBRL instancecreation

See Note #2

COMBO_CF_EDIT_REQUEST

COMBO_CF_EDIT_REPLY

COMBO_CF_EDIT In Sync

Out Sync

Combo edit request /reply service whichcalls the combo editonline validationlogic.

Note. #1—GL subscribes to these accounting entries and writes them to their corresponding accounting table.When you run journal generator, it sends back the accounting message with the following updated fields.Please check with the individual products to see if they utilize this update message from GL.

Note. #2—Target node is typically an external node that accepts and handles XBRL documents.

See Also

PeopleSoft PeopleTools PeopleBook: Integration Broker, "Sending and Receiving Messages"

PeopleSoft Enterprise Components PeopleBook: “Activating Messaging EIPs"

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “UnderstandingPeopleSoft Commitment Control”

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,” UsingXBRL to Produce Balance Sheets and Income Statements, page 588

Publishing FullSync DataThis type of EIPs are used to initialize setup tables.

This is typically a one time setup using messages with the _FULLSYNC suffix and the FUND_LOADmessage. Use the Full Table Publish utility to publish the entire setup table. The subscribing database willerase it’s own setup table and synchronize itself by populating data from the message. Make sure you haveactivated the full publish rules before you run this process. Navigation to the Full Data Publish utility is:

Enterprise Components, Integration Definitions, Initiate Processes, Full Data Publish.

Publishing Sync DataThis type of EIPs are used to synchronize incremental change of setup table.

Setup messages with a _SYNC suffix are associated with Setup pages. When you makechanges to a corresponding setup data, such as ChartFields and Detail Calendars, a messagewill be published automatically when you save the page.



Using Transaction and Other MessagesThis section describes how accounting entry messaging, commitment control messaging,and the integration broker work.

Accounting Entry Messages

Accounting entries are generated in each PeopleSoft sub-system applications and then published to PeopleSoftGeneral Ledger. Some of them use the Batch Data Publish utility while others have their specific proceduresto publish. Please refer to the application PeopleBooks on how to publish data from them.

After receiving the accounting entries, you will run Journal Generator to create journal entries into PeopleSoftGeneral Ledger. Journal Generator updates the accounting table and publish the updated data back to PeopleSoftsub-system applications over the same EIP it receives accounting entries. Fields updated by Journal Generatorincludes Journal ID, Journal date, Journal line number, Fiscal year, Accounting period, GL_distrib_status

Please check with the individual PeopleSoft sub-system products to see if they utilize thisupdate message from PeopleSoft General Ledger.

Commitment Control Budget Update Messages

These steps describe how commitment control budget update messaging works.

1. HCM Northern Payroll enters and generates commitment control budget data and sends them toGeneral Ledger using the COMMIT_CNTRL_BUDGET_UPDATE message.

2. Upon receiving the message, the subscription process runs automatically and updates the budget journaltables, and then initiates the Budget Post process to update the commitment control ledgers.

Note. Refer to the General Ledger Integration Map using the following reference.

HCM Account Code Integration

HCM maintains their account code table with data from the Financials ChartField combination data table andthe Financials SpeedTypes. HCM uses account codes extensively in their systems to represent a combinationof ChartField values. Do not confuse these account codes with the account ChartField in Financials.

Financial users access the Build Combination Data page to initiate the build process and to publishChartField combination data to HCM and Learning Solutions over the HR_ACCT_CD_LOAD message.A message publishes data from a selected process group and sends it to HCM to convert it into theiraccount codes. For further details please read the concerning Account Codes.

SeePeopleSoft Human Resources PeopleBooks: “Commitment Accounting ProcessingControl Tables,” Setting Up Valid Account Codes

When you add or update a user SpeedType and you selected the Publish check box, the ChartFieldcombinations of that SpeedType publish to HCM and convert into their account code.



Note. You use the Publish Data check box to control whether you want to send the ChartField values ofthe new or updated SpeedType to PeopleSoft HRMS, which uses the SpeedType to update its AccountCode table. The checkbox is visible and available if the SpeedType is auserSpeedType and the HRMSinstallation option is checked. If the checkbox is visible but grayed on the page, the message objectHR_CHARTFIELD_COMBO_SYNC is not activated. When available, this checkbox always default tounchecked. This option is not part of the SpeedType data and thus not saved with your SpeedType definition.

See Also

PeopleSoft 8.8 Human Resources PeopleBook: “Manage Commitment Accounting,”Commitment Control Processing Control Tables

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Editing ChartFieldCombinations,” Understanding ChartField Combination Editing

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Understanding CommitmentControl Integration with PeopleSoft and Third-Party Applications”

Integrating PeopleSoft General Ledger with PeopleSoftEnterprise Performance Management Budgeting

Enterprise Performance Management (EPM) defines and initiates the PeopleSoft GeneralLedger to PeopleSoft Enterprise Management Budgeting integration using the ETL tool. Thisprocess initiates from the PeopleSoft Budgeting application .

Note. You must refer to the PeopleSoft 8.8 Budgeting PeopleBook for details concerning how to use this feature.

This section also describes where to run the process to to import data from PeopleSoftEnterprise Management Budgeting.

See Also

PeopleSoft 8.8 Budgeting PeopleBook: “Integrating with PeopleSoft Financial Management Applications,”Using Imformatica Powermart ETL and Data Loader Utility, and Importing Data Into General Ledger

Page Used to Import the Enterprise PerformanceManagement Budgeting


Importing Budgeting Data BP_RUN_CNTL_LEDGER Set Up Financials/SupplyChain, Product Related,Budgeting, Import BudgetLedger

Imports a ledger containingbudgeting data



Importing Data from Enterprise PerformanceManagement BudgetingAccess the Importing Budgeting Data page.

Note. You must refer to the PeopleSoft 8.8 Budgeting PeopleBook for details concerning how to use this feature.

SeePeopleSoft 8.8 Budgeting PeopleBook: “Integrating with PeopleSoft Financial Management Applications”:Using Imformatica Powermart ETL and Data Loader Utility, and Importing Data Into General Ledger

Importing Journal EntriesIn this section we describe how to:

• Import journals from flat files using GL_JRNL_IMP.

• Use Spreadsheet Journal Import.

• Import Commitment Control budget journals from flat files.

Importing Journals from Flat Files Using GL_JRNL_IMPUse the following references for details concerning how to use GL_JRNL_IMP.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Using the Journal Entry Import Process, page 159

PeopleSoft PeopleTools PeopleBook: Integration Tools and Utilities, "File Layouts and Data Interchange"

Using Spreadsheet Journal Import (GL_EXCL_JRNL)Use the Spreadsheet Journal Import process to streamline journal import and simplify journal data entryusing Microsoft Excel. Spreadsheet Journal Import uses a front-end interface that provides you with aneasy-to-follow menu for entering data, specifying defaults, and importing journals. With Spreadsheet JournalImport, you can enter foreign, base, and statistical journals as well as adjusting journal entries.

Once you have created you spreadsheet, the Spreadsheet Journal Import utility usesone of the two import methods:

• The online import method uses XML link technology and sends data over the internet, processesthe import request, and then replies to the Excel interface.

• The batch import method requires that you write the data into a file, submit and upload oneor more files through the browser, and then initiate the Spreadsheet Journal Batch Importprocess (GL_EXCL_JRNL) to process the import.

See Also

Chapter 9, “Using Spreadsheet Journal Import,” page 173



Importing Commit Control Budget Journals Using Flat FilesYou import Commitment Control budget journals using flat files.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “UnderstandingCommitment Control Integration with PeopleSoft and Third-Party Applications,” IntegratingCommitment Control with PeopleSoft Applications.

See Chapter 6, “ Integrating and Transferring Information Among Applications ,” IntegratingPeopleSoft General Ledger with PeopleSoft Applications, page 67.

Transferring Ledgers for ConsolidationThe Ledger Load for Consolidation EIP interfaces and transfers both detail and summaryledger data from one database to another.

In this section we describe how to:

• Publish and subscribe ledger data.

• Import information to a ledger using flat file ledger import process (GL_LED_IMP).

Publishing and Subscribing Ledger DataGeneral Ledger both publishes and subscribes using this EIP on the application message LEDGER_LOAD.You can publish ledger data from a regional database to the corporate database for the purpose of consolidation.On the subscription side, summary ledger data is stored in the summary ledger tables directly, while detailledger data is subscribed in a staging table for processing by the Ledger Load process (GL_LED_LOAD).

You initiate the ledger publish process (GL_LED_PUB) from General Ledger > ConsolidateFinancial Data > Publish Ledgers within the regional database. Ledgers are protected by theAllow Ledger Load Update option on the Ledgers For A Unit page.

See Also

Chapter 16, “Performing Financial Consolidations,” Using the Ledger Interface Utility , page 359

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Defining Ledgers for a Business Unit

PeopleTools PeopleBook: PeopleSoft Integration Broker,” Defining Message Channels and Messages

Importing Information to a Ledger Using GL_LED_IMPIn addition to using publish and subscribe to bring over ledgers, you can also import data using the Flat FileLedger Import process (GL_LED_IMP) to import standard detail ledgers and standard budgets ledgers.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Importing and Exporting Ledgers




CHAPTER 7

Optimizing General Ledger Performance

This chapter provides an overview of reducing run time for background processing and discusses how to:

• Use non-shared tables.

• Use indexes.

• Use partition IDs.

• Use ADB incremental calculations.

• Update summary ledgers incrementally.

• Optimize PS/nVision performance.

Understanding Optimal General Ledger PerformanceMany functions in PeopleSoft General Ledger are run as background processes. If more than oneprocess tries to use the same database table at the same time, contention can occur for the same rowof data. This can cause rollbacks. Data retrieval can be slowed by queries on non-indexed data.Some strategies for avoiding system slowdowns are covered in this chapter.

PrerequisitesBegin enhancing the performance of your online pages, Application Engine, SQRs, andCOBOL background processes only after you:

• Configure your ChartFields.

• Populate your records with data.

• Understand General Ledger background processing.

Using Non-Shared TablesThis section discusses how to:

• Use PeopleTools temporary tables.


Optimizing General Ledger Performance Chapter 7

• Use GL non-shared tables.

• Set up GL non-shared tables.

Pages Used to Set Up GL Non-Shared Tables


Shared Table Statistics TEMP_TBL_STATS General Ledger, MonitorBackground Process, SharedTable Statistics

Access a log containing eachtime the process used ashared base working tablebecause a non-shared tablewas not available.

Non-Shared TableMaintenance

NONSHARED_TBL_ASGN General Ledger, MonitorBackground Process,Non-Shared TableMaintenance

Add, delete, or modifynon-shared tables.

Using PeopleTools Temporary TablesPeopleTools provides a feature that allows applications to dedicate a specific instance of a PeopleToolstemporary table for each program run. This concept is similar to the GL Non-Shared tables designin that it drastically reduces the risk of table contention. This feature is supported in some of theGL Application Engine processes that use the PeopleTools temporary tables. These General LedgerApplication Engine processes use the PeopleTools temporary tables:

• Journal Edit.

• Combination Editing.

• Allocation Copy Utility.

• Inter/IntraUnit Common Processor.

• Journal Generator.

• Summary Ledger Build.

SeePeopleTools PeopleBooks: “PeopleSoft Application Engine,” Temporary Tables

Using GL Non-Shared TablesApplication Engine and COBOL SQL processes use GL non-shared tables to increase performance.

The records PS_LEDGER (ledger) and PS_JRNL_LN (journal line), which includes the PS_JRNL_HEADER(journal header) record are the most heavily accessed records. While these two records are thefocus of this chapter, you can apply the same techniques to any record.

Several GL Application Engine and COBOL SQL processes use working temporary tables, calledbaseworking tables, to process large volumes of temporary data. Base working tables are shared workingtemporary tables that can be used by more than one program to process temporary data. You can potentiallyhamper performance if you run concurrent processes that use the same base working table.

To increase performance, these processes use GLnon-shared tablesin place of the shared working tables:

• ADB.


Chapter 7 Optimizing General Ledger Performance

• Allocations.

• ChartField Combination Build.

• ChartField Combination Editing.

• Closing.

• Commitment Control Budget Checking.

• Commitment Control Budget Closing.

• Commitment Control Budget Post.

• Journal Edit.

• Journal Generator.

• Journal Posting.

• Ledger Load.

• MultiCurrency.

• Open Item Accounting.

• Summary Ledger.

GL non-shared tables are defined by appending the non-shared table version number, TEMP_TBL_NUM,from table TEMP_TBL_ASGNM to the base working table TEMP_TBL_NAME. Only the processthat reserves the non-shared table can process transactions against that table.

The PeopleSoft General Ledger Application Engine and COBOL SQL processes use tableTEMP_TBL_ASGNM to identify and reserve a non-shared table. This table defines thefields in the TEMP_TBL_ASSNM table.

Column Description

TEMP_TBL_NAME Base working table name.

TEMP_TBL_NUM Non-Shared table version number.

IN_USE_SW Indicator to determine if the non-shared table is in use.

PROCESS_INSTANCE The process instance of the process that has thisnon-shared table reserved.

Process for Assigning GL Non-shared Tables

The process first determines if a non-shared table exists by matching the base workingtable name (shared table) of the processes to the base working table name in TEMP_TBL_ASGNM that has the IN_USE_SW indicator set toN.

• If a non-shared table is available, it reserves it. The process reserves the non-shared table byupdating the IN_USE_SW indicator toY in the TEMP_TBL_ASGNM table. No other process



can use the non-shared table as long as the IN_USE_SW indicator isY. The process updates thePROCESS_INSTANCE to identify which process has the non-shared table reserved.

• If a non-shared table is not available, the process uses the base working table (instead of a non-sharedtable) and inserts a row into the TEMP_TBL_STATS table. This table provides a way to monitorthe load of base working tables and the statistics can be useful to decide whether more non-sharedtemp tables are needed. This table defines the fields in TEMP_TBL_STATS.

Column Description

TEMP_TBL_NAME Base working table name.

PROCESS_INSTANCE The process that attempted to reserve a non-sharedtable.

DATE_ASSIGNED Process run date.

Setting Up GL Non-Shared TablesThe TEMP_TBL_ASGNM table is delivered with four non-shared tables for each base workingtable. If these do not meet your processing requirements, use the GL Non-Shared Table Maintenancepage to add more non-shared table entries to TEMP_TBL_ASGNM.

Adding a Non-Shared Table

To add a non-shared table:

1. Determine if you need to create a non-shared table entry to TEMP_TBL_ASGNM. Using theShared Table Statistics page, check the TEMP_TBL_STATS table to determine if the usage ofthe base working table justifies creating additional non-shared tables.

2. Create the GL non-shared table in PeopleSoft Application Designer. Save the record definition froman existing non-shared table or the base working table. PeopleSoft recommends that you createthe non-shared table from existing non-share tables rather than the base working table. Non-sharedtables usually have less fields in the index structure that the base working table.

3. Create a GL non-shared table entry in TEMP_TBL_ASGNM using the GL Non-Shared Tables page.

4. Add a non-shared table for a custom base working table. If you have created your own base workingtables, add non-shared table entries to your Base Working Tables entries (repeat steps 1 to 3). Keepin mind that most non-shared tables do not require any unique indexes.

Viewing Shared Table Statistics

Access the Shared Table Statistics page.

This log helps you to determine whether you need to create additional non-sharedtable entries in TEMP_TBL_ASGNM.

Note. The process inserts a log in TEMP_TBL_STATS only if the non-shared table entriesexist for the base working table in TEMP_TBL_ASGNM.



Record (Table) Name Enter the name of the shared table whose statistics you want to view.

Non-Shared Tables Identifies the number of non-shared tables currently created.

Table Name Base working table name.

Process Instance The process that attempted to reserve a non-shared table.

Job ID The Job ID of the process that attempted to reserve a non-shared table.

Date Assigned Run date of the process that attempted to reserve a non-shared table.

Adding Instances of General Ledger Non-Shared Tables

Access the Non-Shared Table Maintenance page.

You add instances of non-shared tables to the TEMP_TBL_ASGNM table so that the non-sharedtable is available for use by the batch processes.

To add a new instance of a GL non-shared table, enter its name in the Table Name field and click the Searchbutton. All instances of that table are displayed. Click the Add icon to add a new instance.

Table Name Enter or select the name of the table that you want to maintain or leavethe field blank to view all tables available for maintenance.

Process Instance Enter or select a specific process instance to maintain or leave the fieldblank to view all process instances available for maintenance.

Reset Click to reset the In Use field to No. which removes the check markfrom the check box. Select Reset regularly for all tables, but makesure that no one is using the system.

If a process aborts, the In Use flag remains set to Yes. In order to free thetable for other processes, the you must reset the flag to No.

Warning! If you reset a process instance while it is running, it can cause data integrity problems.

Reset does not clear the contents from a table. However, the table is cleared the next time it is assigned.

Table Name Displays the name of a non-shared table. You can select another name.

Number Displays the instance number of the non-shared table. Youcan change this number.

In Use Indicates whether the non-shared table is being used in a process. ClickReset to remove the check mark and change the selection to N.

Note. See previousWarningbefore you select Reset.

Process Instance Instance number of the batch process that has reserved this non-shared table.



Note. If you are using your own customized base working table, make sure the table name doesnot exceed 12 characters. The total character length of a table cannot exceed 15 characters, soyou must allow for three characters for the non-shared table instances.

These menu paths identify where the base working tables are assigned to the processes that support theuse of non-shared tables, as well as the temp tables whose base table names are fixed.

If the temporary table is specified in the ledger template or some definition pages, the recordname is listed in the Dynamic Working Tables column below; otherwise the record nameis listed under the Fixed Working Tables column.

Process Menu PathDynamic Working

TablesFixed Working

Tables

ADB General Ledger, Ledgers,Templates, Record Definitions

General Ledger, Average DailyBalance, ADB Definition

Ledger ADB Tmp

Ledger ADB Tmp2

Ledger ADB Tmp3

Batch Work Record

ADB_TREE_SEL

Allocations N/A (Using App Engine TAOtables)

N/A TREE_SELnn_R

Closing General Ledger, Ledgers,Templates, Record Definitions

Closing Tmp

Closing RE Tmp

Closing Account Tmp

Closing Journal Header Tmp

Closing Journal Line Tmp

Closing Journal Line Tmp2

Ledger Load General Ledger, Ledgers,Templates, Record Definitions

Led Load Temp Record

Led Load Temp Record 2

Multicurrency General Ledger, Ledgers,Templates, Record Definitions

MultiCurrency Tmp

MultiCurrency Tmp1

TREE_SELnn_R



Process Menu PathDynamic Working

TablesFixed Working

Tables

Post Journals General Ledger, Ledgers,Templates, Record Definitions

Ledger Tmp

Ledger Tmp2

Journal Line Tmp

GL_OI_TMP

JRNL_HDR_SEL

JRNL_HDR_TMP

JRNL_VAT_TMP

JRNL_XRF_TMP

Open ItemReconciliation

General Ledger, Ledgers,Templates, Record Definitions

Journal Line Tmp GL_OI_TMP

Budget Processor General Ledger, Ledgers,Templates, Record Definitions

Ledger Tmp

Ledger Tmp2

KK_ACT_TMP

KK_LQD_TMP

KK_SRC_TMP

KK_TDET_TMP

KK_TSUM_TMP

Post BudgetJournals

General Ledger, Ledgers,Templates, Record Definitions

Ledger Tmp

Ledger Tmp2

Journal Line Tmp

KK_BDHDR_TMP

KK_TREE_SEL

Close Budget N/A N/A CFV_SEL

KK_RSCFV_SEL

TREE_SELnn_R

Note. The ChartField Combination Build & Editing, Commitment Control Budget Checking,Commitment Control Budget Post, Commitment Control Budget Closing, Consolidation, Equitization,and OpenItem Accounting processes are not listed in the table above because the processes usea predefined base working table that use non-shared tables.

Using IndexesIn this section, we discuss how to:

• Identify appropriate Indexes.

• Select indexes.

• Make the rules practical.

• Use indexes in the demo system.



• Optimize Indexes.

Depending on the database platform, volume and distribution of data, the correct index can speedprocessing greatly. As the volume of data in your ledger and journal tables grows, periodicallyreview the plan and indexes to ensure that they remain efficient.

The indexes delivered with the demonstration database were created for small amounts of data andare specific to the delivered sample ChartFields—these may be inappropriate for your situation.Develop indexes specific to your own data and configuration.

Indexes are sets of information used to access data in a record. They are stored separately from the records butupdated simultaneously when records are updated, inserted, or deleted. Each of your records should have oneunique index. This provides a valuable edit function by preventing duplicate rows of data from being addedto the database. Add more indexes to improve performance when locating and accessing the data.

When you create a record in PeopleSoft Application Designer, the system automatically creates a uniqueindex with the same name as the record. So, journal line record (PS_JRNL_LN) is created with a uniqueindex, usually named PS_JRNL_LN. This unique index includes all the keys that were identified on therecord. The combination of these keys should identify one unique row of information.

PeopleSoft Application Designer sometimes creates additional indexes when you add a record. These aregenerated from fields identified as alternate search keys on the record itself and are not included in the uniqueindex mentioned above. For example, the GL_ACCOUNT_TBL has Alternate Search Keys designated onAccount Type and Description fields. When the table is created in Application Designer, two additional indexes(PS0GL_ACCOUNT_TBL and PS1GL_ACCOUNT_TBL) is created with each of these fields listed. Theseadditional indexes are always termed duplicate indexes, because they may not point to unique rows of data.

PeopleSoft General Ledger includes system tables that enable you to view the created indexes and their columns.

Identifying Appropriate IndexesHere we discuss the system analysis you need to do before you implement special indexes.

Now that you know what indexes PeopleSoft General Ledger creates, determine whether the deliveredindexes are suitable or if you need additional indexes. Changes to the ChartFields, changes in configuration,and differences in data content all affect the indexes and their effectiveness.

Capturing SQL Statements

First, determine the indexes currently used by your system. Do this by capturing the SQL statementsexecuted by the system, then running them in isolation to determine the database access path for retrievingthe data. For either real-time on-line access or batch processes, you can identify the SQL statementsthat access the ledger and journal line tables and whose performance may be a concern. Please refer toPeopleTools PeopleBooks on how to turn on the SQL trace for on-line and batch processes.

SeePeopleTools PeopleBook: “PeopleSoft Process Scheduler”

See”PeopleTools PeopleBook: “PeopleSoft Server Tools”



Establishing a Baseline

Second, determine the efficiency of your current indexes; you need to establish a method for measuringprogress as you make changes. A baseline timing is generally used for comparison when trying outdifferent indexes. Time either the individual SQL statements or the entire process, so long as youhave some way of determining progress as you proceed with the tuning.

Determining Indexes Used

Third, you have a list of processes that access the primary records. Now you need to determine whichindexes each process currently uses. In other words, you need to determine the database access path thatthe system takes when the statement is actually executed. Because the database access path might changeaccording to differing volumes of data, it is important to execute the plan on approximately the same amountof data that the table contains in a production environment. It might be appropriate to take a copy of yourproduction database specifically for the purpose of tuning the indexes. Generally, when obtaining planinformation, you are not actually executing the statements; check your database administrator documentationto be sure this is the case before executing any statements in your production environment.

Each platform has a process for determining the database access path that the engine uses to accessdata for the SQL statement. Below we present a brief outline of the DB2 approach.

Note. Refer to your database administration documentation for your platform andconsult with your database administrator.

If your system is on DB2, create a PLAN_TABLE if your database does not already have one. Asample CREATE statement is in your DB2 Performance Tuning documentation.

Include the SQL statement in the following and execute it:

DELETE FROM PLAN_TABLE WHERE QUERYNO=nnn;

EXPLAIN PLAN SET QUERYNO=nnn FOR

statement;

Where nnn is a number you assign to this statement.

Retrieve the plan from PLAN_TABLE with the following SELECT:SELECT QBLOCKNO, PLANNO, TNAME, ACCESSNAME, METHOD,

ACCESSTYPE, MATCHCOLS, INDEXONLY, PREFETCH, SORTC_GROUPBY

FROM PLAN_TABLE

WHERE QUERYNO=nnn

ORDER BY QBLOCKNO, PLANNO;

The table contains other plan information, but these are the most pertinent columns for your purposes.

Note. If your system is on Oracle, consult with your database administrator to create a databaseaccess path if your database does not already have one.

Selecting IndexesBefore determining whether the index is appropriate, you need to know how the databaseengine selects indexes. In general, consider these basic rules:

• The columns in the “where” clause are used when deciding on an index.



On most platforms, the database engine takes equality statements, “like” statements, andless-than/greater-than statements into consideration. For example, in the statement “where business_unit= ’NEWGN’ and accounting_period >= 1 and <= 12..” the application engine uses both thebusiness_unit and accounting period when it accesses the data. With a “like” clause, if a specificvalue is passed, the system uses it to select an index; however, if the field contains a wild card (’%’),the system ranks the column lower in priority when it determines an index.

• Each platform has specific index limitations.

For example, SQLServer and Oracle platform indexes do not perform well with a “NOT = ” or “!=”statement. In DB2, any column after a range (>, <) is not used when the system selects an index. Be sure toconsult your platform system administration documentation for the specific index limitations on your system.

• The system looks at cardinality. Cardinality refers to the number of unique values in a column.

For example, if you only have one business unit in your organization, then the business_unit columnin the ledger record only has one value in it—very low cardinality. In the demo database, the accountcolumn is always entered and has many unique values, so the cardinality is fairly high.

To determine cardinality on a particular ChartField, issue a SQL statement that selects count(*)from the table in question. The value returned is the number of entries in the record. Ingeneral, high cardinality fields should be included in the index.

• The columns that are used to join records should generally be included in an index.

These are the fields in a “where” statement used to join one record to another. These columnstend toward low cardinality, and the optimizers do not rate equality to another column nearly ashigh as equality to a bind variable. For these reasons, columns used to join tables are usuallyin the unique index but generally are not included in all other indexes.

• The system only uses an index up to the point that a column in the index is not included in the “where” clause.

For example, if the Journal Line record has an index that includes Business Unit, Journal ID, and JournalDate, but our “where” clause includes only Business Unit and Journal Date, the index is only effective forthe business unit. The journal date provided is ignored because the journal ID information is not included inthe “where” clause. For this reason, the sequence of the fields in the index is very important.

• The system uses the size of the record and the selectiveness of the index to determinewhether the index or full-table scan is more efficient.

This is sometimes referred to as the filter factor. The effective filter factor for an index is the combinedcardinalities for the index columnsactually usedin a particular access.

For example, if an index is built over FISCAL_YEAR, LEDGER, and ACCOUNT, and the table containsfour years, five ledgers, and 800 accounts, the potential filter factor is 1/(4*5*800), or 1/16000, or0.0000625. (In a real-world data distribution, the filter factor would not be this good, but it would still bequite good unless the data is very skewed.) However, if the ACCOUNT field in the index could not be usedbecause of the nature of the criteria for it, the filter factor would be only 1/20, which is not very selective.In general, an index should point to around 10% - 15% of a record in order to be efficient.



Making the Rules PracticalTo put these rules to practical use, you need to identify SQL statements that performed badly, andexamine each “where” clause in those SQL statements. What you are trying to obtain from each SQLstatement are the columns, accessed in the “where” clause, that you believe are acceptable to the systemfor index selection. In other words, you get to count all the columns that use an equal value, but noneof the columns using “between” logic, and so on. To logically view this huge amount of information, itis best to make a chart with the columns in the “where” clause across the top and the origin of the SQLstatement down the left side. As you go through each SQL statement, place anX in the box under thecolumn that the index is likely to use. Create a chart for each record that concerns you.

Viewing a Sample "Where" Clause Chart

The following is a sample "where" clause chart for the ledger record with SQL statementsgenerated from the demo database:

BU LED ACCT DEPT STAT FY PERIOD CURR

ONLINE

BudgetDetail

X x x x x x x

X x x x x x x x

Budget Copy X x x

X x x x

BudgetSpread

X x x x x x x

X x x x x x x x

LedgerInquiry

X x x x x x

X x x x x x x

X x x x x x x

X x x x




InterUnitInquiry

X x x x x

TimeSpanInquiry

X x x x x x

JournalEntry

X x x x x x x x

REPORTS

GLS7004 X x x x x

GLS7005 X x x x x

GLS1003 X x x x x x

GLS7002 X x x x

GLS7003 X x x x x

BATCH

Posting X x x x x x x x

Closing X x x x

X x x x

X x x x x

X x x x x

X x x x

SummaryLedger

X x x x

X x x x




Consolidate x x x x x

X x x x x x

Currency X x x x x x x x

Armed with these charts and the rules of indexing, now work to create indexes that access the records morequickly. Looking across the columns used in ledger “where” clauses, assess the viability of each column.

Business unit is included in every “where” clause, but in the demo database there are only 79 ofthem. One of these, US001, is used much more frequently than in the others, so the cardinality isrelatively low. Because it is always used, you will probably include it in indexes.

The ledger column is also included in each clause, but the cardinality is low (three are usedin the LEDGER table and one used the majority of the time).

Account is used in a good percentage of the “where” clauses and is required in most of the onlineinquiry transactions. The cardinality is also high (735 unique values of account in the ledger tablein the demo database), so this is a good possibility in an index.

Other ChartFields, including DEPTID, PRODUCT, and PROJECT, are lumped together because the demodatabase does not require them and accepts a wildcard in their place on the inquiry pages. This wildcardgenerates a “like” SQL statement that works well if you supply the field with a value; it is less efficient ifthe field is left as a wildcard (’%’). If you have ChartFields that you always enter, you should include thesein the index in the same way the account field is included. You might also want to consider making any“always enter” fieldsrequiredon the inquiry pages to make the select statements more efficient.

Fiscal year is included on nearly every “where” clause. At present the cardinality is relatively low(3 - 4 different values); however, expect it to increase as time goes by. Accounting period is usedon a good number of “where” clauses, again with limited cardinality.

Currency code is included in many of the “where” clauses. There are many values in the currency code record,but in practice the vast majority of transactions in the ledger record have a currency code of USD, so thecardinality of this field is also relatively low. Therefore, this column might not be included in most indexes.

Hints for Indexing

The following hints can help you create better indexes:

• Strive for the minimum number of indexes to accomplish the processes.

- Each index has to be updated every time an update, insert, or delete is performed on the underlyingtable; so each index has an overhead cost associated with it. In considering the right number of indexesfor a table, be sure to consider the use of the table. Fairly static tables (like Chartfield tables) canhave numerous indexes with relatively little negative impact because they are frequently accessedand rarely updated. Other tables, however, are updated continually and each additional index couldmake quite a difference in the amount of time it takes to perform these functions.



- These extra indexes on fairly static tables (like Chartfield tables) are not a problem. However,if there are list items designated on records that are never used as edit (prompt) tables and theindex generated is not assisting any processing, you have actually created additional overheadduring record updates and inserts without any benefit. The bottom line is that you shouldcarefully consider designating fields as alternate search key fields.

- On Oracle, the more fields the merrier. In tests the optimizer seems to prefer an index that hasall the values in the “where” clause over one that is more specific but smaller. In general, Oraclechooses the unique index over all others if it can. Although this is acceptable in most instances,there are times when another index enhances the performance considerably. To get the alternateindex recognized by the cost based optimizer it is often necessary to make it appear more attractiveby putting in as many columns as possible from the “where” clause.

- If two indexes are tied (judged of equal effectiveness), the optimizer chooses the index referencedfirst in the “where” clause. Because the vast majority of “where” clauses that access thePS_LEDGER table begin with equality checks on business unit and ledger, these commonfields are included at the beginning of most of the Oracle indexes.

• Sometimes it is beneficial to put a column in the index that would not usually be included in a“where” clause but is usually retrieved from the table when the table is accessed.

- An example of this is the account type on the GL_ACCOUNT_TBL. This column is generally accessedwhen the table is queried, and adding this column to the index might prevent table access when onlythe account type is needed. The Alternative Search Key indexes actually do this for us in most cases,because these indexes generally contain descriptions, and this information is frequently accessed whena code table is accessed. This approach is only useful if it prevents table access in some instancesand does not interfere with the normal operation of the index in other situations.

- For this reason, these columns are generally at the end of the indexes. Some customers have experiencedan improvement in background processing against the ledger record when the posted total amount fieldis added to the end of the duplicate indexes, because it results in an index-only scan. During testing onthe demo database, there was some negative impact on the online performance, so this field was notadded to the delivered indexes. But it might be worth testing in your production environment.

• The system is specific about the indexes chosen.

Sometimes the most well thought-out index does not get used as expected or does not yield the expectedresults. Test the new index, taking a look at the plan to be sure it is used, then take another timing to comparethe new index access with the original baseline timing. Based on the results, you might need to adjust thesequence of the columns in the index or the columns included in the index to find the optimal combination.

Once you find the best combination for the SQL statements under review, run through all the processesagain. Sometimes one new index can cause changes in the indexes used by other processes. Oftenthe change is good, but sometimes it is worse, and more evaluation is required.

Indexes in the Demo SystemPeopleSoft delivers the sample database with the indexes listed below. The columns in the indexes have beennoted, followed by a brief explanation of why each index is included and how it affects performance. Theseindexes are included in PeopleSoft Application Designer and are created when indexes are created for the record.



Note. It might be beneficial to drop these indexes before performing a large load or update. Loading datainto a table means that each of the indexes on the table need to be updated; this can amount to considerableoverhead when many rows are inserted. It might be beneficial to drop these indexes, load the data or performthe background process, and then run the script again to recreate the indexes on the tables.

PS_LEDGER: (All Platforms)

PS_LEDGER PSCLEDGER PSFLEDGER

BUSINESS_UNIT FISCAL_YEAR ACCOUNT

LEDGER LEDGER ACCOUNTING_PERIOD

ACCOUNT BUSINESS_UNIT PRODUCT

ALTACCT ACCOUNT FISCAL_YEAR

DEPTID

OPERATING UNIT

PRODUCT

FUND_CODE

CLASS_FLD

PROGRAM_CODE

BUDGET_REF

AFFILIATE

AFFILIATE_INTRA1

AFFILIATE_INTRA2

PROJECT_ID

BOOK_CODE



PS_LEDGER PSCLEDGER PSFLEDGER

GL_ADJUST_TYPE

CURRENCY_CD

STATISTICS_CODE

FISCAL_YEAR

ACCOUNTING_PERIOD

PS_LEDGER

This is the original, unique index from PeopleSoft Application Designer, which was left in place as the uniqueindex. Change this index to reflect your own ChartField configuration. Because it is generated from ApplicationDesigner, making the record changes to the LEDGER record should produce the correct index for you.

Some platforms have a 16-column limit for indexes and this index already has 21 columns, andis not supported for some platforms (namely Microsoft SQL Server, DB2/Unix, and Informix).PeopleSoft resolves this by creating ’Function Indexes’ behind the scene with index basedon a field which is the concatenation of all the key fields.

While no PeopleSoft processes rely on the presence of the unique index on a table, your databasemanager should carefully consider any decision not to have one. A unique index is a data safeguardenforced by your database engine. It guards against duplicate data resulting from a process thatdoes not work correctly or from invalid data in an SQL script.

Note. If you are a DB2 customer and you want to partition the dataset based on fiscal year, you may wantto delete this index and replace it with a unique index that has Fiscal Year as the leading field.

SeePeopleTools PeopleBooks: “PeopleSoft Application Designer,” Understanding FunctionalIndexes and Planning Records, Control Tables, and TableSets

PSALEDGER (All Platforms Except Oracle)

Experienced PeopleSoft General Ledger customers recognize this index. This is the most efficient indexfor PS/nVision reporting and also helps out the Closing and Summary ledger COBOL processes. Notethat it is similar to the PSBLEDGER index except that it starts with Fiscal Year (so those processesthat do have an equality for accounting period choose the “B” version over this one). The index alsoincludes the Account field, thereby adding efficiency for any “where” clause selecting specific accountvalues. This is an index you probably have to modify to reflect your own ChartField configuration.The last fields of this index should include the ChartFields with the highest cardinality that are usuallyentered and used in “where” clauses. Avoid adding all your ChartFields because that would create agreat deal of overhead when any of the ChartFields are added or changed in the ledger. It is usuallybest to include the minimum number of fields to do the job in an index.



Note. If you are doing PS/nVision reporting on your summary ledger, be sure to create this index for thesummary ledger record. Please see the notes under the PSBLEDGER index for additional thoughts on this topic.

PS_LEDGER (All Platforms Except Oracle)

PSALEDGER PSBLEDGER

ACCOUNT ACCOUNTING_PERIOD

FISCAL_YEAR FISCAL_YEAR

BUSINESS_UNIT LEDGER

LEDGER BUSINESS_UNIT

The leading field on this index is the Account field. This index helps speed performance on all processesthat access the ledger using a specific account selection. This includes the Trial Balance and General LedgerActivity SQRs, as well as the COBOL processes of Closing and Consolidations. Online, this index helps in thebudget entry process and the ledger inquiry pages. You need to modify this index for your own ChartFieldconfiguration. The leading fields on the index should be the ChartFields that are always entered and have thegreatest cardinality. Because the Fiscal Year, Business Unit, and Ledger fields are consistently requested withthe Account field, they are also on the index and should be appropriate on your version of the index.

PSBLEDGER

This index begins with the Accounting Period field and is called into use when the accounting periodand fiscal year are specified without specific ChartField references. This enhances performance in theClosing Trial Balance SQR, Closing and Summary Ledger COBOL processes, and the online budgetcopy process. You should be able to use this index as is without modifications.

Note. The summary ledgers delivered with the demo database (PS_S_LEDGER_ACCTS,S_LEDGER_ACTDEP, and PS_S_LEDGER_SUM) realized performance gains in the summaryledger background process when this index was created for them. The “B” type of index might bebeneficial for your own summary ledgers. Because this index is similar to the PSCLEDGER index,you may want to do some timings and analysis before deciding if the additional indexes on your ownsummary ledgers are worth the additional overhead during inserts and updates.

PS_LEDGER: (Oracle only)

PSDLEDGER PSELEDGER

BUSINESS_UNIT FISCAL_YEAR

LEDGER ACCOUNTING_PERIOD

FISCAL_YEAR BUSINESS_UNIT



PSDLEDGER PSELEDGER

ACCOUNTING_PERIOD LEDGER

CURRENCY_CD ACCOUNT

STATISTICS_CODE PRODUCT

ACCOUNT PROJECT_ID

AFFILIATE

CURRENCY_CD

PSDLEDGER (Oracle Only)

This index is used in the same way the PSALEDGER index is used on the other platforms—to optimizeperformance in online processes, SQRs, and COBOL processes when the entire ledger key is not specified.Specifically, the Trial Balance and General Ledger Activity SQRs, the Closing and Consolidations COBOLprocesses, and the budget and ledger inquiry online pages use it. The index leads off with the common fields ofBusiness Unit and Ledger and includes more of the “where” clause columns than its PSALEDGER counterpart.As in the PSALEDGER version, when building this index on your production system you should change theAccount field in the demo database to be the ChartFields you always enter that have the highest cardinality.

PSELEDGER (Oracle Only)

The closing process Closing Trial Balance SQR and the closing COBOL process primarily use this index.The summary ledger COBOL process also favors it. If you do not run either of those processes (or run theminfrequently), you might not need this index. To modify the index, replace the demo ChartFields with yourown. The leading ChartFields should be those you always enter that have the highest cardinality.

PSWLEDGER

The PSW index is used to build the search index for database platforms that have the16–column limit on indexes. This index will not be a unique index, instead, the concatenated’Functional Index’ plays the role of the unique index.

PS_JRNL_HEADER (All Platforms)

The same analysis processes were applied to the JRNL_LN and JRNL_HEADER records, and thefollowing indexes are delivered with your demo database as a result of this study:

PS_JRNL_ HEADER PSCJRNL_ HEADER PSDJRNL_ HEADER

BUSINESS_UNIT PROCESS_INSTANCE JOURNAL_ID

JOURNAL_ID JRNL_HDR_STATUS JOURNAL_DATE



PS_JRNL_ HEADER PSCJRNL_ HEADER PSDJRNL_ HEADER

JOURNAL_DATE JRNL_PROCESS_REQST BUSINESS_UNIT_IU

UNPOST_SEQ UNPOST_SEQ

PS_JRNL_HEADER (All Platforms — Continued)

PSGJRNL_HEADER PSHJRNL_HEADER PSIJRNL_HEADER

PROCESS_INSTANCE PROC_PART_ID BUSINESS_UNIT

SYSTEM_SOURCE BUSINESS_UNIT PROCESS_INSTANCE

LEDGER_GROUP LEDGER_GROUP

JRNL_PROCESS_REQST JOURNAL_ID

JOURNAL_ID JOURNAL_DATE

UNPOST_SEQ

PS_JRNL_HEADER

This is the unique index created by PeopleSoft Application Designer. It is used each time thejournal is referenced by the key values. This includes the OpenItem and SJE Status SQRs, postingand journal edit COBOL processes, and online journal inquiry and entry processes. You shouldnot need to change this index for any ChartField configuration.

PSCJRNL_HEADER

Because the leading field on this index is PROCESS_INSTANCE, the index helped speedprocessing in the journal posting and journal edit COBOL jobs where the statements select fromthe journal header based on PROCESS_INSTANCE. If you run those jobs, you want this index.You should not need to change it for any ChartField configuration.

PSDJRNL_HEADER

This index is used by the online system to obtain the journal headers and journal lines for InterUnit subjournals.

PS_JRNL_HEADER (All Platforms Except Oracle)

PSAJRNL_HEADER PSBJRNL_HEADER

ACCOUNTING_PERIOD JRNL_PROCESS_REQST

SOURCE BUSINESS_UNIT



PSAJRNL_HEADER PSBJRNL_HEADER

FISCAL_YEAR LEDGER_GROUP

BUSINESS_UNIT

LEDGER_GROUP

PSAJRNL_HEADER

This index is selected when the accounting period, source, and fiscal year are specified in the “where”clause. The sequence of the columns was chosen by cardinality for the demo database (source hasseven unique values and accounting period has 12). You need to analyze your own system to determinewhich column should come first—source or accounting period. Choose the column with the greatestcardinality (unique values). This index helps speed processing in the Trial Balance and GeneralLedger Activity SQRs and in the online inquiry and journal unpost functions.

PSBJRNL_HEADER

This index helped the Posting process by indexing on the JRNL_PROCESS_REQST field. Youshould not need to change this index for ChartField configuration.

PS_JRNL_HEADER (Oracle only)

PSEJRNL_HEADER PSFJRNL_HEADER

BUSINESS_UNIT JOURNAL_ID

LEDGER_GROUP SOURCE

JRNL_HDR_STATUS JRNL_HDR_STATUS

FISCAL_YEAR BUSINESS_UNIT

ACCOUNTING_PERIOD LEDGER_GROUP

PSEJRNL_HEADER (Oracle Only)

This index assists the processing of the SJE Status SQR and the Journal Post and Allocations COBOLprocesses. No modifications should be necessary for ChartField changes.

PSFJRNL_HEADER (Oracle Only)

The only COBOL process that uses this index is the Allocations process. If you donot run that job, you should not need the index.



PS_JRNL_LN (All platforms)

PS_JRNL_LN PSDJRNL_LN PSFJRNL_LN

BUSINESS_UNIT PROCESS_INSTANCE JOURNAL_DATE

JOURNAL_ID BUSINESS_UNIT BUSINESS_UNIT

JOURNAL_DATE ACCOUNT UNPOST_SEQ

UNPOST_SEQ JOURNAL_ID

JOURNAL_LINE JRNL_LN_SOURCE

LEDGER

PS_JRNL_LN

This is the unique index created by PeopleSoft Application Designer. It matches the keys onthe parent record (PS_JRNL_HEADER) with the addition of the Journal Line field. This isused in processing when you update the journal line in the Posting and Journal Edit COBOLprograms, and online Posting and Journal Update processes.

PSDJRNL_LN

This index assists the COBOL processes in accessing the journal line information. It is used in thebackground Journal Edit process, and should not require modification for ChartField changes.

PSFJRNL_LN

This index is used by the GLAJES SQR report, Posting, Consolidations, Currency Translation, andAllocations COBOL processes, as well as the online inquiry and posting pages.

PS_JRNL_LN (All Platforms Except Oracle)

PSAJRNL_LN PSBJRNL_LN

ACCOUNT JOURNAL_ID

BUSINESS_UNIT JOURNAL_DATE

CURRENCY_CD BUSINESS_UNIT

UNPOST_SEQ



PSAJRNL_LN

This index facilitates those queries that look for a specific match on the Account ChartField. Itincludes the additional fields of Business Unit and Currency Code, because those fields are consistentlyincluded in the "where" clauses of these statements. It enhances performance in the GLAOITEMSQR, Journal Posting COBOL process, and the online Journal Inquiry and Unposting processes. Ifchanges are made to the ChartFields, you need to modify this. You should include the ChartFieldthat is always entered and has the greatest cardinality in this index.

PSBJRNL_LN

The items in this index are similar to the unique index except that the sequence is different andthe JOURNAL_LINE field is left off. The JOURNAL_LINE field was eliminated because it isalmost never referenced in “where” clauses. The sequence was changed because JOURNAL_ID is ahigh-cardinality field and is frequently referenced in select statements. In the select statements thatspecify JOURNAL_ID, the BUSINESS_UNIT, JOURNAL_DATE, and UNPOST_SEQ fields arealso referenced; so these were included on this index in order of cardinality.

This index is frequently used: in the GLALEDGD, GLALEDGS and GLAJES SQRs as well as the Posting,Consolidations, Currency Translation, and Journal Edit background processes. Online, it is used on theinquiry and posting pages. This index should not require changes for ChartField configuration.

Note. Consider adding the JOURNAL_LINE and LEDGER to the end of the PSBJRNL_LN index andmaking it the unique index (eliminating the existing PS_JRNL_LN index). This is an option because theorder of the index columns can differ from PeopleSoft Application Designer field sequence.

PS_JRNL_LN (Oracle only)

PSEJRNL_LN

BUSINESS_UNIT

CURRENCY_CD

ACCOUNT

PSEJRNL_LN (Oracle only)

This index is comparable to the PSAJRNL_LN index, except that the sequence is different.Consistent with the cost-based optimizer approach, the more common fields (Business Unit andCurrency Code) are included at the beginning of the index. The SQR processes of Trial Balance,General Ledger Activity, and OpenItem Status use this index.

Optimizing IndexesThis section discusses how to optimize indexes.



Updating Statistics

Once the indexes are created, you must tell the system to use these new indexes, by “updatingstatistics.” The specifics vary by platform; refer to the chart below. After new indexes are created,or after inserting or deleting substantial rows of data from existing tables, you should run the updatestatistics procedure. The purpose of this procedure is to update the system tables with index andtable information to assist the optimizer in choosing the most efficient index for an operation. If thisprocedure is not performed frequently, your system performance could suffer.

Platform Method to update statistics

DB2 Batch RUNSTATS process, by Table Space.

ORACLE ANALYZE TABLE xxx COMPUTE STATISTICS

ANALYZE INDEX xxx COMPUTE STATISTICS

For large tables, it is faster to replace COMPUTEwith ESTIMATE. Determine through testing whetherestimated statistics yield optimum access plans.

Table Seeding

Indexes are delivered for several temporary tables. These include tables such as LEDGER_TMP, which holddata only for the duration of a specific process. Because the tables are generally empty, running updatestatistics on the empty version of the table causes the optimizer to think that the table is always empty andto favor a full-table scan instead of using the index. For this reason, a script is available to seed thesetemporary tables with 100 rows of data for the purpose of updating the statistics on the index.

The script is delivered in your SQL subdirectory and is called SEEDGL with the SQL extensionappropriate to your database platform. The script inserts 101 rows of data into the temporarytables and runs the update statistics command on the seeded table. The tables that are seeded arethe and PSTREESELECT05, PSREESELECT06, PSTREESELECT08, and PSTREESELECT10 tocorrespond to the length of the ChartFields delivered with the demo system.

If rows currently exist in your PSTREESELECTxx tables, you should not delete this data. Thesystem populates these rows when you execute a PS/nVision report. These rows correspondto a control table named PSTREESELCTL, and if removed by them, result in incorrect data orno data in your PS/nVision report the next time you execute it.

Please review each script before running to ensure that the key values loaded do not conflict with anythat would be used by the existing system, and to determine if changes are needed for any specificmodifications you might have done. When running the scripts in your production environment, besure that you seed the PSTREESELECT tables that correspond to the field length of your ChartFields;these are the PSTREESELECT tables that are used in your environment.

Note. If you are a DB2 customer, you can maximize the benefits of seeding these tables, by seeding themwith the cardinality that is correct for your particular environment. A script named SEEDMULT.DMS isan example of seeding the PSTREESELECT06 table with correct cardinality. Please use this version,rather than the above versions, when seeding the PSTREESELECT tables.



Physical Performance Considerations

Even the best index planning and execution cannot overcome performance problems caused by disk andindex fragmentation. Fragmentation happens over time as records are deleted, updated, and added tothe database. When new records are inserted, the system places the new information wherever space isavailable—not necessarily in the same location as the rest of the physical table. As records are deleted,gaps might be left in the physical space that the record occupied which can or cannot be filled in withnew information. As the physical locations of these records become more spread out, the system mustwork harder to find the specific record you requested, and response time suffers. Both indexes andtables can become fragmented and hamper performance, so it is important to take the steps outlined inyour database administration documentation to eliminate database fragmentation.

Using Partition IDsWhen you have a large volume of transactions to process in a limited run-time, use partition IDs to enable thejournal posting processes (GLPPPOST) to run in parallel. Partition IDs enable you to group your transactiondata into mutually exclusive sets, ending contention between processes for the same row of data duringposting. This eliminates possible delays due to halted processes and database rollbacks.

Only after your system has been in production for several months is it practical to implementpartition IDs. It requires reevaluation at regular periods to ensure your system stayswithin the limits of your batch run-time window.

It is crucial that you understand your data structure before attempting to use partition IDs. Analyze thevolume of your transactions by business unit and ChartField, and divide them into transaction groupswith roughly equal numbers of transactions. Using your analysis, create a business unit/ChartFieldcombination scheme to classify the transactions into mutually exclusive data sets. Then, createa partition ID for each a business unit/ChartField combination.

You may want to monitor the duration of batch processing to ensure your partition IDs remaineffective over time. This can provide advance warning of changes in your system’s batchprocessing requirements, as well as changes in your business.

To use partition IDs, first, define them using the Partition ChartField Entry ProcessPartition page. Then, specify your partition IDs in the request pages for the Journal Edit(GL_JEDIT) and Journal Post (GLPPPOST) processes.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Defining Process Partitions

Using ADB Incremental CalculationsThe ADB Calculation process (GL_ADB_CALCX) supports these optimizing features:



• Incremental calculations to compute the Average Daily Balance.

This method leverages from prior period aggregate and ending balances to calculate therequested period average. All adjustments are automatically applied to the average balancesbefore calculation of the requested period averages.

• Non-shared tables to process temporary data, including the tree selector tables.

• Archiving ledger data. This includes the ADB ledger and the ADB target ledgerwhich holds the calculated averages.

Other ways that the ADB Calculation process supports system optimization is that it enables customers to:

• Filter transactions posted the ADB ledger to control the volume of data.

• Partition the calculated averages to different target ledgers.

The process also enables the customer to specify a calendar ID to the target ledger. For example,customers can specify a monthly calendar to store the MTD balances.

See Also


Updating Summary Ledgers IncrementallySummary ledgers can be updated incrementally. There are two ways to do this:

• From Process schedule run option Increment.

• During posting to the detail ledger, thus keeping summary ledger synchronized with its detail ledger.

The objects and fields needed to support this feature are the following:

• The Summary Ledger Stage Tbl (table). This is defined on the Ledger Template page.It is a copy of posted detail ledger transactions.

• The Status table (accessed from the Summary Ledger Status page). This contains a row for each businessunit, summary ledger, fiscal year and accounting period (summary). The status table also includes a datetime stamp with the date and time when the system writes the row into the status table.

• The Ledger Tmp (a summary ledger temporary table). This is defined on the Ledger Template page. Itis a copy of the summary ledger table and is used when you specify incremental updating.

• The Enable Incremental Sum Ledger option on the Ledgers for a Unit Journal Post Options page.This option indicates whether rows for business unit/detail ledger are staged.

If this option is not selected, the staging process is bypassed. When staging is bypassed, no summaryledger for this business unit/detail ledger can be incrementally updated.

• The Skip Summary Ledger Update option. This option is located on both the Journal PostRequest page and the User Preferences General Ledger page. It specifies whether to updatesummary ledgers during a specific run of a posting process.

• The Post to Summary Ledger option on the Ledger Set page. This option enables a specificbusiness unit/summary ledger to be incremented from posting.



The incremental summary ledger update process flow is as follows:

1. Summary Ledger process (initial summary ledger creation):

• On the Summary Ledger process request page, if the Request Type isCreate, the process creates initialsummary ledger data for the given business unit/summary ledger/accounting periods.

• The process inserts a row into the Status table for each business unit/summaryledger/accounting period processed.

2. The Journal Post process:

• If the Enable Incremental Summary Ledger option is selected on the Ledger for a Unit - Posting Optionspage, the process inserts rows into the Staging table with data posted to the detail ledger.

• If the Post to Summary Ledger option on the Ledger Set page is selected, the process incrementallyupdates the summary ledger from the Staging table. (See step 3 for details.)

3. Summary Ledger Process (incremental update):

• For a given business unit and detail ledger, the process determines the summary ledgers and accountingperiods to process based on the ledger set, the Post to Summary Ledger option, and the Status table. Onlycombinations with status entries and with the Post to Summary Ledger option selected are processed.

• If the ledger has not yet been created, the process performs the creation directly from the ledgertables. Otherwise, it updates the ledger incrementally from the staging table.

• For each business unit/summary ledger/accounting period processed, the processinserts a row in the Status table.

• The process cleans up the Staging table by deleting rows with dttm_stamp earlierthan the minute stamp of related status rows.

Note. If the incremental update is initiated from the Summary Ledger Process Requestpage, the Request Type must be Increment.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,”Combining Accounts Using Summary Ledgers

Optimizing PS/nVision PerformanceThis section discusses:

• Tree joins.

• Combination rules.

• Capturing SQL.

PS/nVision is a complex tool, capable of producing a great variety of reports from a variety of databasetables. The SQL statements it generates are not necessarily complex, but they are very sensitive tothe performance of the underlying database, especially in the following areas:



• Large tables (ledgers often have millions of rows) make efficient use of indexes essential.

• The use of trees and reporting (security) views cause multiple tables to be joined. The efficiency withwhich the database processes these JOINs dictates most of the performance of PS/nVision.

Unlike traditional background reporting tools, PS/nVision supports interactive, focused reporting with aprobing or querying approach to accessing the database. PS/nVision queries tend to be more numerous thantraditional report writers are, but also more focused on the specific data that you want to see.

Tree JOINsPS/nVision relates tree node criteria to data tables by joining the data table to a tree selector table. Thisselector table contains a row for every detail range defined for the tree in the Tree Manager, and is keyed byPROCESS_INSTANCE (a system-generated constant number for all the rows representing a particulartree) and tree node number. Because some database platforms only join tables efficiently if the field sizesmatch, we use up to 30 selector tables, one for each supported ChartField length. Each selector table hasRANGE_FROM_nn and RANGE_TO_nn columns matching the corresponding ChartField size.

The following is a typical SELECT for selection via nodes on a single tree.

SELECT L.TREE_NODE_NUM, SUM(POSTED_TOTAL_AMT)

FROM PS_LEDGER A, PSTREESELECT06 L

WHERE A.LEDGER=’ACTUALS’

AND A.FISCAL_YEAR=1991

AND A.ACCOUNTING_PERIOD BETWEEN 1 AND 9

AND A.ACCOUNT>=L.RANGE_FROM_06

AND A.ACCOUNT<=L.RANGE_TO_06

AND L.PROCESS_INSTANCE=198

AND (L.TREE_NODE_NUM BETWEEN 16 AND 30

OR L.TREE_NODE_NUM BETWEEN 35 AND 40)

GROUP BY TREE_NODE_NUM

The parts of this statement in boldface accomplish the tree criteria selection. The GROUP BY clausereturns an answer row for each node that has a detail range attached to it; these node numbers are usedto post amounts from the answer set into the appropriate rows of the report.

Combination RulesPS/nVision endeavors to retrieve the data for each report instance with as few SELECTs as possible. Itexamines all row criteria to determine which can be combined, and does the same for column criteria. Itthen builds a SELECT to retrieve each intersection of a combined group of rows with a combined groupof columns. You should understand the following built-in rules when designing indexes:

• Different ledgers cannot be combined.

• Different TimeSpans cannot be combined.

• nPloded rows or columns cannot be combined with non-nPloded rows or columns.

• To be combined, two or more rows or columns must have criteria for the same set ofChartFields, and each ChartField’s criteria must be of the same type (selected tree nodescannot be combined with selected detail values).

• If criteria for a ChartField are specified by tree node, they can only be combined if they use the same tree.



• If the combined rows or columns have identical criteria for a particular ChartField, the criteria areincluded in the “where” clause but no “group by” on that field is required. If different rows/columns inthe group have different criteria, PS/nVision adds this field (or the corresponding tree node number) tothe “group by” clause to retrieve a value for use in posting the answer set to the report.

• A single SELECT can retrieve amounts for multiple combined rows and columns.

• Different scope instances are retrieved with separate SELECTs.

Capturing SQLTo examine the SQL produced by PS/nVision, capture the statements in one of two ways:

• Use the Options Trace option on the Excel menu. This causes PS/nVision to display each SELECTused for retrieving labels or amounts in a dialog. Select the text with the mouse, then copy it to theclipboard, then use or the Edit, Paste command to paste the text into another application such as Notepador a text editor. Then save the text to a file or work with it within the application.

Note. If you want to capture the SQL but do not want to wait for it to execute, select the Excel OptionsSimulated Run option. PS/nVision generates all the SQL, but will not execute SELECTs for amounts.

• Select the PeopleTools SQL trace through the Utilities menu. This causes all SQL statements executed byPeopleTools to be written to a file called ~DBG0001.TMP in the Windows TEMP directory (often C:\TEMP).This trace shows timings, but does not include SQL that was not executed due to the Simulated Run option.


CHAPTER 8

Making General Ledger Journal Entries

This chapter provides an overview of PeopleSoft General Ledger journal entries and discusses how to:

• Create journal entries.

• Create inter/intraunit journal entries.

• Post to the Summary Ledgers table and the Summary Ledger Staging table.

• Create standard journal entries.

• Edit journal entries.

• Copy journal entries.

• Delete journal entries not yet posted.

• Use the Flat File Journal import process (GL_JRNL_IMP).

• Use the Spreadsheet Journal Import process (GL_EXCL_JRNL).

Understanding PeopleSoft General Ledger Journal EntriesThis section lists prerequisites and common elements and discusses:

• Prerequisites

• Common elements used in this chapter.

• Journal components and processing.

• Journal entry identification and masks.

• Journal entry processing.

PrerequisitesYou may want to set up security for your profiles and then define user preferences for General Ledger.

• PeopleTools Security

For security, anyone who uses or accesses the general ledger must have a user ID. User IDs aredefined in PeopleTools, Security, User Profiles. Several pages require a user ID and validateagainst the user profile before admitting a user to the page.

• User Preferences


Making General Ledger Journal Entries Chapter 8

Many applications, however, have application-specific preferences. In PeopleSoft General Ledger,these preferences are defined on the User Preferences - General Ledger page. Many of the preferencesspecified on this page apply to entering, editing, and processing journals. While you can restrictusers to specific business units, TableSets, ledgers, and so forth, the User Preferences pages defineonly default settings for pages and reports. Theydo notnecessarily define security.

• Enable Document Sequencing for each business unit if you use document sequence numbersto sequentially number your journals and open item journals.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining User Preferences”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Securing Your System”

Journal Component s and ProcessingAt a minimum, a journal in PeopleSoft General Ledger consists of a header and entry lines. The headercontains the information that uniquely identifies the journal (business unit, journal ID, and journal date) andoptions that enable you to quickly set up adjusting and reversing entries and foreign currencies. Journal entrylines record the monetary and statistical amounts and the ChartField values associated with each transaction.

Once you enter the header and line information, your journals are ready for processing. However, if youwant a greater degree of control over the journal entry process, you can incorporate:

• Control totals that ensure accuracy and are particularly helpful when you enter a large number of lines.

• Journal approval, based on rules you define, to ensure that only those journals within thelimits you specify are approved for further processing.

• Document sequencing to track journal IDs sequentially.

In PeopleSoft General Ledger, standard journal entries (SJEs) enable you to automate the entry of similaror identical journals. There are three types of SJEs: recurring, template, and spread. Arecurring journalentry is any entry periodically generated according to a schedule, such as monthly rent, lease payments,and depreciation expenses. Atemplatejournal entry is a data-entry model for other journals that you canautomatically reproduce on a fixed schedule—like recurring SJEs—or use on request. Aspreadjournal entry isan entry in which the entire journal’s amount is spread proportionately across the different periods.

See Also

Chapter 10, “Processing Journals,” page 189

PeopleTools PeopleBooks: PeopleSoft Process Scheduler

Journal Entry Identification and MasksWhen you create a new journal, the system prompts you with the three keys that uniquely identifythat journal: business unit, journal ID, and date. You can enter your own ID or let the systemassign one. You can reuse the same journal ID throughout the year, or even within the sameaccounting period, changing only the date for each instance.

After you create a journal, you can search by document sequence number on::


Chapter 8 Making General Ledger Journal Entries

• Create Journal Entries - Find an Existing Value search criteria page.

• Review Journal Status - Find an Existing Value search criteria page.

• Open Item Maintenance page.

• Review Open Item Status page.

• Review Financial Information - Journals - Journal Inquiry Criteria

The document sequence number for a journal also appears on:

• The Journal Entry Detail Report (FIN2001).

• The General Ledger Activity Report (GLS7002).

This table demonstrates an example where your subsidiaries and parent organizations canrecord monthly payroll transactions using the journal ID PAYROLL because each journal isuniquely identified by business unit, journal ID, and date.

Business Unit Journal ID Date Total Debits

US002 PAYROLL 09/04/01 400,000

US004 PAYROLL 09/04/01 430,000

US002 PAYROLL 09/18/01 420,000

US004 PAYROLL 09/18/01 440,000

Using these three keys to identify a journal makes finding, tracking, and organizing journalsmuch easier. It also makes it possible to copy related journals and group them by ID. Youcan use the same journal IDs and dates across business units.

The journal ID maskenables you to specify a prefix for naming journals when you are using NEXT to generatejournal IDs. A 10-character alphanumeric ID identifies journals. The system automatically appends the prefixthat you specify to the journal IDs. For example, if you specify ALLOC as the journal ID mask, and your journalID on the flat file is NEXT, your allocation journal IDs might be ALLOC00001, ALLOC00002, and so on.

Warning! If you plan to use journal ID masks, reserve a unique mask value for the regularjournal entry process. Ensure that your regular journal entry users communicate with users whoperform other processes, such as consolidations and allocations, so that no other process createsthe same mask value as that used in regular journal entry.

Journal Entry ProcessingPeopleSoft GeneralLedger offers several ways to process journals. Once you have completedthe header and line entries, you can save the journal from any of the journal entry pages, or youcan do one of the following from the Journal Entry - Lines page:

• Request to edit.



• Request to budget check.

• Request to post.

Most users enter and save journals, leaving editing, budget checking, and posting for later.

See Also


Creating Journal EntriesThis section discusses how to:

• Enter journal header information.

• Specify journal entry currency defaults.

• Specify journal entry reversal options.

• Specify commitment control options.

• Enter journal line information.

• Specify processing selection criteria.

• Initiate the calculate amount process.

• Use separate debit and credit.

• Retrieve a system rate.

• Enter an exchange rate manually.

• Calculate using the calculate rules.

• Select a journal entry template.

• Set journal entry copy-down options.

• Enter projects information.

• Access the secondary ledger lines.

• Use statistics codes.

• Specify journal entry totals.

• View journal entry errors.

• Specify journal entry approval options.



Pages Used for Journal Entry


Journal Entry − Header JOURNAL_ENTRY1 General Ledger, Journals,Journal Entry, Create JournalEntries

Enter journal headerinformation that uniquelyidentifies the journal:business unit, journalID, and journal date. Italso contains options forsetting, adjusting, andreversing entries and foreigncurrencies.

Journal Entry CurrencyDefault

JOURNAL_ENTRY_CUR On the Journal Entry -Header page, click CurrencyDefaults.

Enter the currencyinformation that defaults tothe individual journal lines.

Exchange Rate Detail EXCH_RT_DTL On the Journal EntryCurrency Default page, clickExchange Rate Detail.

Shows the exchangerate details based on theinformation you entered inthe Journal Entry CurrencyDefault page.

Journal Entry Reversal JOURNAL_ENTRY_RVR On the Journal Entry −Header page, click Reversal.

Specify the date of anautomatically reversed entry.

Commitment Control JOURNAL_ENTRY_KK On the Journal Entry− Header page, clickCommitment Control.

Specify the commitmentcontrol amount type fora journal if you use thecommitment control option.

Journal Entry − Lines JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries, Lines

Record the transactionsmaking up the journal—thedebit and credit entries.Once you enter the headerand lines, you can requestfurther processing on thepage.

Journal Entry Template List JOURNAL_ENTRY_TMP On the Journal Entry − Linespage, click Template List.

Select the template thatdefines which columnsappear in the lines scrollarea. Also specify the fieldvalues to be copied down tonew lines when you click theInsert Journal Lines button.

Change ChartField Values JRNL_SUSP_CF_SEC On the Journal Entry − Linespage, click Change Values.

Apply changes to alldisplayed journal lines byentering the existing fieldvalue and the correct value.

Project Information PC_FIELDS On the Journal Entry − Linespage, click the link underProject.

Enter project informationfor the journal line. Thisinformation becomesavailable in PeopleSoftProjects so you can keepcomplete financial control ofa project.



Page Name Object Name Navigation UsageSecondary Ledger Lines JOURNAL_ENTRY_SEC Click the Secondary

Lines link on the JournalEntry - Lines page.

View secondary ledger lines.

Journal Entry - Totals JOURNAL_ENTRY_T_IC General Ledger, Journals,Journal Entry, Create JournalEntries, Totals

Specify control debit andcredit amounts, unit valueof statistical entries, andthe number of lines. Thesecontrols enable you toenforce a greater degreeof control over the journalentry process.

Journal Entry - Errors JOURNAL_ENTRY_E_IC General Ledger, Journals,Journal Entry, Create JournalEntries, Errors

Determine which errors thesystem encountered.

Journal Entry - Approval JOURNAL_ENTRY_A_IC General Ledger, Journals,Journal Entry, Create JournalEntries, Approval

Select the current journalfor approval if you usePeopleSoft Workflow toapprove journals for posting.

Entering Journal Header InformationAccess the Journal Entry − Header page.

Journal Entry - Header page



Note. This page or related pages operate in deferred processing mode. Most fields are not updated or validateduntil you save the page or refresh it by clicking a button, link, or tab. This delayed processing has variousimplications for the field values on the page—for example, if a field contains a default value, any value youenter before the system updates the page overrides the default. Another implication to keep in mind is that thesystem updates quantity balances or totals only when you save or click the Calculate Amount button.

Journal ID If the Use Next Journal ID option is selected for your user preference, theJournal field is unavailable and defaults toNEXT. When the journal is saved,the system automatically assigns the next journal ID to the journal.

Date Determines the period to which the system posts the journals, unless it is anadjusting entry. For business units using a holiday list ID, the journal entrypage requires that journal date be a working day, regardless of the accountingperiod. If you initially enter a date on a non-working day, you’ll receive anerror message suggesting the next working day. You must manually enter thisor another working date before entering Journal Entry pages.

Long Description Identifies the purpose or explaining any anomalies in the transaction. The first30 characters of your description appears in prompt lists for this journal.

Ledger Group Select the ledger group to which this journal posts.

Auto Generate Lines Select this check box if the ledger group contains multiple ledgers.

If the Keep Ledgers in Sync (KLS) option for MultiBook ledgers is selectedon the Ledger Group − Definition page, the Auto Generate Lines check boxshould always be checked so that the system automatically generates journallines to support transaction detail for each ledger in the group. For example,if you enter a two-line journal entry for a ledger group that contains threeledgers, the journal entry or edit process generates two lines for each ledger.

Ledger Select a ledger within the ledger group to indicate that all the journallines must be posted to that ledger, or leave this field blank to indicatethat the journal lines can be distributed to secondary ledgers. Use thisfield only if the ledger group contains multiple ledgers, KLS is off, andthe Auto Generate Lines option is not selected. If the ledger group is acommitment control ledger group, you must select a ledger.

Once you start entering journal lines, you cannot change the values in theLedger Group, Auto Generate Lines, or Ledger fields. Otherwise, yourjournal lines would be out of sync with your journal header.

Adjusting Entry Select Adjusting Entry from the drop down list if this is an adjusting entry.The journal entry posts to the displayed adjustment fiscal year and period.

If this is not an adjusting entry, you cannot change the accounting period value.The journal date determines the accounting period to which the entry posts.



Note. Year-end adjustments are segregated from the regular accountingperiod so as not to distort period-to-period results; they are recorded inspecial adjustment periods (as defined on the detail calendar). They areposted to the target ledger in the adjustment year and period specified as theadjustment period default on the Maintain Open Periods page. (You canoverride the default adjustment period from the Journal Entry page.) If youdo not specify an adjustment year and period on the Maintain Open Periodspage, the system doesnot allow adjusting journal entries. You can postprior year adjustments while processing the current year activity.

Source Determines various options for entering and editing journals. Select a journalsource that best represents how the journal should be processed. Once youstart entering journal lines, however, you cannot change the journal sourceselection if the journal is originally created using the Journal Entry component.

Reference Number Refers each journal back to a document, person, invoice, date, or any otherpiece of information that helps you track the source of the transaction.

Period Change the adjustment period by clicking the look up box to displaya list of valid adjustment periods (as defined on the detail calendar).Select the one to which you want this entry posted.

SJE Type (standard journalentry type)

Leave this field blank if this is not a standard journal. SelectModel ifthis is a model journal that you use to create other standard journals.There are several process restrictions on a model SJE journal. It cannot bebudget checked, posted, or submitted to workflow approval, and journaledit does not calculate value-added tax (VAT) or subtract inclusive VATamounts from the journal line. In addition, once validated by the journaledit process, the model journal cannot be changed or deleted.

Note. Model journals must be edited and if it is valid thesystem assigns it a status ofM.

ADB Date (average dailybalance date)

Enter the date you want to use for calculating average balances. (Enter this onlyif the ledger to which this journal posts supports ADB reporting.) Normally,the ADB date is the same as the journal date. The ADB date determines forwhich period the average balance is calculated. If you have selected theMaintain Regulatory Balances option for the ledger on the Ledgers For a Unit− Definition page, the system calculates the average balance for both periods.

Journal Class Select this field only for PeopleSoft General Ledger journal entry transactions.Journal classes enable you to categorize journal entries for reporting, aswell as for journal entries loaded from non-PeopleSoft systems.

This field also appears for SJEs and copy journals. And both ofthese options enable you to copy the journal class entered in thesource journal to specified target journals.

The journal suspense correction journal contains the same journalclass value as the journal in error.



The Journal Import process (GL_JRNL_IMP) supports importing ajournal class field value from a flat file.

Save Journal IncompleteStatus

Select this check box when you are unable to enter all journal transactions andanticipate finishing the entries at a later time. When selected, you can enterincomplete journal transactions and save them with a status ofT - Journal EntryIncomplete. If you use the batch edit, posting, or budget checking process, thejournal is bypassed until you complete your entries and clear the check box.

When you complete the journal, clear the check box.

The Save Journal Incomplete Status check box matches thevalue (checked or unchecked) of the same check box on the UserPreferences - General Ledger page.

Transaction Code Specify the code to indicate the appropriate inter/intraunitpayable or receivable account.

The journal suspense correction journal contains the same transactioncode value as the journal in error.

Currency Defaults Click to open the Journal Entry Currency Default page where you enterthe currency information that defaults to the individual journal lines. Thecurrency default you select also appears as part of the link.

Reversal You can generate a reversing entry (as with an accrual) when you post thisentry. To select the date of the reversing entry on the Journal Entry Reversalpage, click Reversal. The Reversal link also displays your reversal preferences.

Commitment Control Click to open the Commitment Control page, where you specify thecommitment control amount type for a control budget. This link isavailable only if you enabled the commitment control on the LedgersFor a Unit, commitment control options page.

See Also

Chapter 14, “Calculating Average Balances,” page 255


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and SupplyChain Management Common Definitions,” Defining Journal Class

Specifying Journal Entry Currency DefaultAccess the Journal Entry Currency Default page.



Journal Entry Currency Default page

Transaction Currency Override the default base currency by selecting a value. You can do thisonly if the Foreign Currency Per Journal option specified on JournalSource, Ledgers For A Unit, and General Ledger Definition, CurrencyOptions page isnot set toNo Foreign Currencies.

If the Foreign Currency Per Journal option is set toOnly One ForeignCurrency, you must specify that foreign currency here. Later, whenyou are entering journal lines, their transaction currency values can beequal to the foreign currency or to the base currency.

Currency Code Defaults to the base code currency for the ledger group.

Rate Type Used to convert amounts.

Currency Effective Date Defaults from the journal date, but you can override it.

Get Rate After you changed transaction currency, rate type, and/or currency effectivedate on this page, click this button to get the new exchange rate retrieved fromthe system setup table based on the new information you just entered.

Exchange Rate Detail Click this link to open the page that displays exchange rate detail information.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” page 277

Using the Exchange Rate Detail PageSee PeopleSoft Global Options and Reports PeopleBook: “Processing MultipleCurrencies,” Maintaining Exchange Rates

Specifying Journal Entry Reversal OptionsAccess the Journal Entry Reversal page.



Journal Entry Reversal page

Select the appropriate reversal option:

Do Not Generate Reversal Assumes no automatic reversal of this entry. This is the default.

Beginning of Next Period Creates a reversing entry dated the first business day of the next accountingperiod. It uses the holiday list ID that you assigned to the business uniton the General Ledger Definition − Definition page to determine the firstbusiness day. If the business unit is not assigned a holiday list ID, thereversing entry is dated the first day of the next accounting period.

If the journal is an adjusting journal, the reversing entry is dated the firstbusiness day of the first accounting period of the next fiscal year.

End of Next Period Creates a reversing entry dated the last business day of the next accountingperiod. It uses the holiday list ID that you assigned to the business uniton the General Ledger Definition − Definition page to determine the lastbusiness day. If the business unit is not assigned a holiday list ID, thereversing entry is dated the last day of the next accounting period.

If the journal is an adjusting journal, the reversing entry is dated the lastbusiness day of the first accounting period of the next fiscal year.

Next Day Creates a reversing entry dated the next business day. It uses the holiday listID that you assigned to the business unit on the General Ledger Definition −Definition page to determine the next business day. If the business unit is notassigned a holiday list ID, the reversing entry is dated the next day.



Adjustment Period Creates a reversing entry to the adjustment period you select. Whenyou select this option, you also must enter the adjustment period andreversal date. Enter these values in the corresponding AdjustmentPeriod and Reversal Date fields. The reversal date is used to populatethe journal date and fiscal year of the reversing entry.

If you enter a date on a nonworking day and there is a holiday list ID assignedto the business unit, you’ll receive an error message. The system won’t resetthe reversal date, and you must re-enter a date that is a working day.

On Date Specified By User Enables you select any date in the calendar. When you select thisoption, you must also enter the Reversal Date.

If you enter a date on a non-working day, and there is a holiday list ID assignedto the business unit, you’ll receive an error message. The system won’t resetthe reversal date; you must re-enter a date that is a working day.

ADB Reversal

If the ledger group supports average daily balance reporting, you must select the method thatis used to populate the ADB date of the reversing entry.

Same as Journal Reversal Creates a reversing entry with the same ADB date as the oneselected above under Reversal so that the journal date and ADBdate of the reversing entry are the same.

On Date Specified by User Enables you select any date in the calendar. When you select this option,you must also enter a value in theADB Reversal Datefield.

If you enter a date on a non-working day, and there is a holiday list ID assignedto the business unit, , you’ll receive an error message. The system won’t resetthe ADB reversal date for you; you must re-enter a date that is a working day.

If you specify an ADB reversal date that is on or before the ADBdate, you will receive an error message.

Important! Reversals are marked valid and ready to post when Post process creates them and you donot need to edit them. When the journal date falls within the journal dates, fiscal year, and open periodsspecified on the Journal Post page, the system posts reversals as soon as they are created.



See Also

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Managing Multiple GenerallyAccepted Accounting Principles (GAAPs) and Prior Period Adjustments,” UnderstandingMultiple GAAPs and Prior Period Adjustments

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Accounting Calendars”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining AccountingCalendars,” Adjustments and Other Special Periods

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Setting Up and Using Multibook Ledgers

Specifying Commitment Control OptionsAccess the Commitment Control page.

See Chapter 21, “Using Commitment Control in PeopleSoft General Ledger,” Entering and ProcessingCommitment Control Journal Entries in General Ledger, page 451.

See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “GettingStarted With Commitment Control”



PeopleSoft Global Options and Reports 8.8 PeopleBook, “Managing Multiple Generally AcceptedAccounting Principles (GAAPs) and Prior Period Adjustments”


Entering Journal Line InformationAccess the Journal Entry − Lines page.



Journal Entry − Lines page (1 of 3)

Journal Entry − Lines page (2 of 3)

Journal Entry — Lines page (3 of 3)

Note. The columns that appear on this page are controlled by your choices on the JournalEntry Template, as well as Customize choices.



Note. This page or related pages operate in deferred-processing mode. Most fields are not updatedor validated until you save the page or refresh it by clicking a button or link or selecting a tab. Thisdelayed processing has various implications for the field values on the page. For example, if a fieldcontains a default value, any value you enter before the system updates the page will override thedefault. Another implication to keep in mind is that the system updates quantity balances or totalsonly when you save or when you click the Calculate Amount button.

Process To perform a task, select the task you want to perform and clickthis button. Choose from:

Budget Check Journal:Select to run the Commitment ControlBudget Processor (FSPKBDP1) process to check the journal linesfor the control budget. The journal edit process must validate thejournal before it can be budget checked.

Copy Journal:Select and click the Process button to access the Journal EntryCopy page. Enter changes in journal information for the newly copied journal.

This is an online copy journal version of the journal copy process that is doneusing process scheduler. Descriptions for the fields on this page are the sameas those described in the section for the copy journal using process scheduler.

See Chapter 8, “Making General Ledger Journal Entries,” CopyingJournal Entries , page 154.

Delete Journal:Deletes the current journal.

Edit ChartField: Initiates the journal ChartField Edit process(GL_JEDIT_CF0) to check if the journal has any ChartField-related errors,including ChartField edit, combo ChartField edit, and alternate account edit.

Edit Journal: Initiates the Journal Edit process (GL_JEDIT_0) immediately.

Post Journal: Initiates the Journal Post process (GLPPPOST)immediately. If the journal requires validation, the Journal Edit processautomatically initiates prior to posting. If you are using PeopleSoftWorkflow and require approval, you’ll receive an error message ifyou select this option for unapproved journals.

Print Journal: When you choose this option and click the Process button, thesystem creates the Journal Entry Detail report (GLC7501, or GLC7502 forseparate debit/credit), which is a printed copy of the journal.

Note. When you selectPrint Journal in the Process field and clickthe Process button, Report Manager and Process Monitor links becomeavailable on the journal entry lines page.

Refresh Journal:Retrieves this journal from the database to the pageagain. You can do this when you think others may have changedthe journal after you originally retrieved it.

Submit Journal:Initiates journal approval through workflow processing.If you are not using PeopleSoft Workflow, you’ll receive an errormessage when you select this option.



Note. Typically, for reasons of efficiency, you edit journals and post laterusing background processing. If you want to edit and post more quickly,however, you can select the options listed here in this page.

Template List Click Template List to access the Journal Entry Template List page in whichyou specify a previously created template that defines which columns thatappear in the Lines scroll area. Fields are visible on journal lines unless youcreate specific journal entry templates to make them unavailable.

Search Criteria This link displays after you Save the newly entered journal or when youbring up an existing journal. Select the link to access the GL Journal EntryProcessing page that is used to specify search values for any or all fields listed.

Change Values Select this link to access the Change ChartField Values page to make globalchanges to the ChartField values to use in your journal entry. Enter theexisting field value and the desired value to which you want to change it. Thechange is applied to the journal lines that appear in the Line scroll area.

Inter/IntraUnit Click button to display the number of rows per interunit or intraunit group box.

Errors Only Select this check box to refresh the Line scroll area with only journal lines thatcontain errors. To move sequentially through all journal lines having errors,select the First Row arrow to the left of the chunking text box to move to thefirst line of the journal before selecting the Errors Only check box.

Line Enter the incremental number of lines you want to retrieve in the chunking textbox. The First Row and Last Row arrow buttons on the outer left and rightgo to the beginning and end of the journal lines, respectively. The PreviousGroup and Next Group arrow buttons, on the inner left and right respectively,display journal lines in increment of the number you enter in the chunkingfield. Selecting any of these arrow buttons automatically refreshes the screen.If you have specified search criteria, this navigation (or chunking) displayslines that match the search criteria in the specified chunks. For example, if youspecify that 10 lines be displayed and in the search criteria that you want alljournal lines for Department 100, the system displays an initial ten lines thatcontain Department 100. By clicking the arrow buttons as they are availableyou can display the next 10 lines or the previous ten lines, and so on.

Lines to add Enter the number of lines you want to add when you click theinsert journal lines button to the right.

Journal Lines Addtions, Deletions, and Calculations

You can add journal lines, delete journal lines, and use the journal line calculator by clicking:

To add additional lines to the scroll, enter the number of lines to add inthe Lines to add field, and click the Insert Journal Lines button.

Select the check box next to any journal line that you want to delete,and click the Delete Selected Journal Lines button.



Click the Calculate Amount button in conjunction with the option youselect in the Calculate field on each line to calculate the amount, baseamount, or exchange rate given two of the three values.

See Chapter 8, “Making General Ledger Journal Entries,” Initiatingthe Calculate Amount Process, page 124.

See Also


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Using Entry Events”

Specifying Processing Selection CriteriaClick the Search Criteria link to access the GL Journal Entry Processing Selection Criteria page.

GL Journal Entry Processing - Selection Criteria



When you enter the search criteria, the GL Journal Line Numberfield displays the starting line number for yoursearch. For example, if you enter1 here and10 in the number of lines text box next to the Errors Only checkbox on the Journal Entry - Lines page, the system retrieves journal lines 1 through 10. Enter the selectioncriteria, including any wildcards. These wildcards assist you in finding the exact information you need. Unlessyou enter one of the following wildcards, PeopleSoft General Ledger assumes that you want an exact match:

Initiating the Calculate Amount ProcessThe Calculate Amount process examines changes in the amount-related fields (such as foreign currency,foreign amount, rate type, exchange rate, base currency, and monetary base amount). It calculatesthe unchanged field based on the system rule or the specified rule in the Calculate field. If noneof the amount-related fields are changed on a particular line, no calculation process is initiated onthat line even if the Calculate Amount button is clicked. After the value is calculated, the journaltotals and balancing ChartFields totals are updated to reflect the new totals.

The Calculate Amount process is automatically initiated in the following situations:

• When you save the journal, including when you click the Save button, run remote journaledit, run remote journal ChartField edit, run remote call journal post, run remote call budgetchecking, select copy journal, or submit the journal to workflow.

• When you click the Insert Journal Lines button to insert new lines.

• When you click the Delete Selected Journal Lines button to delete lines.

• When you click the Secondary Lines (>>) button to go to the secondary lines page.

• When you click the Exchange Rate Detail (>>) button to see the exchange rate detail.

• When you click the VAT link to go to the VAT page.

• When you change the business unit or ledger value on the line.

• When you use the SpeedType page to select a speedtype.

The Calculate Amount process performs the following steps:

1. For each journal line on the journal line grid, the system compares all field values with theprior values stored in the buffer to see if there are any changes.

2. If there are any changes on foreign currency, rate type, exchange rate, or base currency, the systemdetermines the new exchange rate. This also initiates exchange rate checking before the new exchange ratecan be accepted. The new exchange rate is then converted to rate multiplier and rate divisor values.

3. If there are any changes in foreign amount, exchange rate, or base amount, the system calculates theunchanged amount based on the system rule or the rule you specify in the Calculate field.

4. The system then adjusts the journal totals and balancing ChartField totals to reflect the newtotals. Even if there is no amount field change, but there is a ChartField value changed, thesystem adjusts the balancing ChartFields totals accordingly.

5. If it is a MultiBook ledger group with auto-generate lines turned on, the system also reflectsthe changes to the corresponding secondary ledger lines.

6. If the account is a VAT-applicable or VAT account, the journal VAT rows reflect the new values.



Note. Online Journal Entry uses deferred processing, which reduces the number of trips to the server.However, the Business Unit and Ledger fields on the journal line grid use non-deferred processing. The mainreason is because changes to these two fields can change the base currency value. Without refreshing the basecurrency value immediately, it could become confusing. The Business Unit field value usually remains thesame unless it is an interunit journal. You can change the ledger value only when it involves a KLS-offMultiBook ledger group with auto-generate lines turned off and when a blank ledger value is on the journalheader. Because both are rare occurrences, server trips should not be an issue in most instances.

Encountering Errors in the Calculate Amount Process

The Calculate Amount process performs various checks, including separate debit/credit amount checking,exchange rate checking. When the process encounters an error, an error message appears and the errorfield or fields turn red. The process does not necessarily stop on an error. If the Calculate Amountprocess has been automatically initiated, the process may behave differently. In some instances, theprocess stops, and in other instances, it continues as noted in the following:

• When you save a journal: the save process stops, an error message appears, and thejournal cannot be saved until you correct the error.

• When you click the Insert Journal Lines button to insert new lines: the insert process stops, an errormessage appears, and new lines cannot be inserted until you correct the error.

• When you click the Delete Selected Journal Lines button: the lines marked deleted are first deleted and thenthe Calculate Amount process is initiated. If the process encounters an error, those marked lines are deleted.

• When you click the Secondary Lines (>>) button to go to a secondary lines page, the ExchangeRate Detail (>>) button to see the exchange rate detail, or the VAT link to go to the VAT page,you cannot transfer to the pages until you correct the error.

When you change the business unit or ledger, or use the SpeedType page to select a SpeedType, the changeson the Business Unit, Ledger, and ChartField field values are processed and the Calculate Amount processis initiated. Even if the calculation process encounters an error, the line is changed.

Enter the business unit or ledger for the journal line in the corresponding fields. Click the buttonnext to the Ledger field to access the Secondary Journal Lines page to view the lines for thesecondary ledger if you have a ledger group with multiple ledgers.

If you are using a SpeedType key to enter frequently used ChartField combinations automatically, click theSpeedType button and select the appropriate SpeedType code. For example, to record revenue from productsales , you could enter an S or SR and click the drop down to quickly find and select the SpeedType namedSREV that you previously defined to populate the account number, sales department, and product code.

In order to record the transaction, you must also enter the account number and ChartField values for operatorunit, department ID, product, and affiliate. Use the bottom scroll bar to view more fields on the grid.

Note. Control accounts and control alternate accounts are not available for online entry in PeopleSoftGeneral Ledger. However, you can choose to use an account that rolls up in the same line item or thatis open to online entry in PeopleSoft General Ledger. PeopleSoft General Ledger also reserves fouraccounts for system-generated balancing lines: suspense, interunit from/to, base currency roundingadjustment, and currency position. You never need to enter these accounts directly. When the journalis edited, the system automatically generates the account and amount.



Click the Projects link to open the Project Information page where you enter project informationif your system has installed PeopleSoft Projects.

The Currency, foreign Amount, Rate Type, Exchange Rate, Exchange Rate Detail , and BaseAmount fields appear even if the transaction item is a base currency line.

For amount fields where you enter both debits and credits to the same field, you enter debits as positivevalues (without a plus sign); however, you must enter credits using the negative sign.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Defining and Using Speed Types

Using Separate Debit and CreditIf you enabled the Separate DR/CR Amount Fields option on the Ledgers for a Unit − Definition page for adetail ledger, amounts appear in the separate debit and credit for both foreign Amount and Base Amount fields.

If you enter a foreign debit and credit amounts on the same journal line, an error message appears, andyou must remove one of the amounts. The same is true if you enter a base amount.

Note. The N/R movement field is available only if you’ve performed the separate debit/credit configuration.

The N/R movement field supports reversing-debit and reversing-credit entries for error correctionfor the separate debit/credit configuration if you chose this option. You can offset a reversingdebit or credit by a natural debit or credit to create a balanced journal entry. For example,suppose that cash is overstated by 1,000 and accounts receivable is understated by 1,000 due toan improper posting. The correcting entry would be as follows:

Accounts Receivable 1,000.00 DR (N) Natural Debit

Cash (1,000.00) DR (R) Reversing Debit

The sign meanings are as follows:

N Natural sign of the monetary amount of the transaction. This is the default.For balancing suspense, base currency rounding adjustments, currencyposition, and interunit from/to lines, this field is alwaysN.

R Reversesign of the monetary amount of the transaction. If the EnableSeparate Debit/Credit option is selected on the Ledgers For A Unit −Definition page and the option is set up in your system, you can togglethis field to represent a reversing debit or credit amount.

Edit error suspense lines have the same value as the suspended line. Accrual reversals populate the movementwith R if the original line wasN, and vice versa. This works the same way for journals being unposted.



If the base currency for the business unit differs from your entry transaction currency (foreigncurrency), enter the rate type and/or the exchange rate to convert to the appropriate base amount. Ifyou want the system to retrieve a defined exchange rate, you must enter only the rate type. Whenyou do, the system automatically populates the Exchange Rate, Base Amount (or Base DR Amountand Base CR Amount if using the Separate DR/CR option) fields.

The Exchange Rate field value must always be1, and the foreign Amount field must equal thebase amount when the journal line is a base currency line.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,”Modifying Tables to Store Separate Debit and Credit Balances

Retrieving a System RateTo retrieve a system rate, the from currency, to currency, rate type, and currency effective date valuesare all required. Without any one of them, the system-derived exchange rate cannot be retrieved.Usually, the from currency is the foreign currency, the to currency is the base currency, and the currencyeffective date is specified on the Currency Default of the Journal Header page.

The system uses the following rules when retrieving the system rate to be used asthe exchange rate for the journal line:

• The system uses the rate type value specified on the line to retrieve the system rate.

However, this does not ensure successful retrieval of a system rate. If there is no market ratedefined for the transaction currency, the retrieved system rate may be zero. In this case, amessage is issued to alert you to the zero exchange rate value.

• If there is no rate type specified on the line, the system rate is zero.

SeePeopleSoft Global Options and Reports 8.8 PeopleBook, “Processing MultipleCurrencies,” Defining Market Rates.

Entering an Exchange Rate ManuallyWhen you manually enter an exchange rate on a foreign currency line, the rate you enter overrides anyautomatically generated system rate. This occurs even if you enter a rate type.

The Rate Type field is clear when you manually enter values. However, the manualrate may not be accepted by the system.

The system performs the following two tests for manually entered exchange rates:

• The system checks the currency quotation method. If the method is defined asTriangulation,Cross Rate as the Primary Visual Rate,andDo Not Allow Cross Rate Override,you cannot entera manual rate. If you try to enter a manual rate, an error message appears, and the system ignoresthe manual rate. This currency quotation method requires the rate type to retrieve the system rateand issues an error message requiring you to enter a rate type to continue.

• The variance between the system rate and the manual rate is calculated, and if it is over thetolerance you defined for maximum variance on the Rate Definition page, aStoperror type or



a Warningmessage appear, depending on the setting. You cannot enter a manual rate if youreceive a stop error type. A warning message allows you to continue.

The system must use slightly different rules to retrieve the system rate when it is to be used asthe base rate for variance checking. The reason is because if the rate type specified on the lineis blank, the system cannot use a zero value for variance checking.

The system must find a non-blank rate type to retrieve the system rate to use as the base rate forvariance checking. The system is subject the following hierarchy of rules:

• Use the rate type specified on the journal line if it is not blank.

• Use the rate type specified on the journal header if it is not blank.

• Use the rate type specified for the ledger on the Detail Ledger Group Definition page.

• Use the required default rate type specified for the ledger on the Detail Ledger Group Definition page.

Note. To use exchange rate variance checking functionality, you must define the market rates.

Manual Rates and Deriving the Rate Multiplier and Rate Divisor

If the manually entered exchange rate passes the two tests for currency quotation method and variance,the system can accept the manual rate. However, because the exchange rate is entered manually as onevalue, the system has to convert it to two values—rate multiplier and rate divisor, depending on whetherthe currency quotation method is direct or indirect and if currency triangulation is specified.

The following conditions hold if true:

• If the quote method is direct and there is no triangulation, the rate multiplier equalsthe exchange rate, and the rate divisor is1.

• If the quote method is indirect and there is no triangulation, the rate multiplier is1,while the rate divisor equals the exchange rate.

• If there is triangulation, the system uses the cross rate entered to recalculate either the rate multiplieror rate divisor based on the recalculate option defined for the currency quotation method.

For example, if the currency quotation method defined for USD to FRF is Direct, Triangulatethrough EUR, Allow Override Cross-Rate, and Cross-Rate Recalculate is USD -> EUR, the systemrecalculates the USD -> EUR rate and leaves the EUR -> FRF rate as is. This means the ratedivisor is recalculated while the rate multiplier is left unchanged.

The following table lists the combinations of currency, rate type, and exchange rate changes and details whichexchange rate for a particular scenario that the system uses for the foreign currency journal line:



Sce

nario

Cur

renc

yC

hang

ed?

Rat

eTy

peC

hang

ed?

Man

ual

Exc

hang

eR

ate

Cha

nged

?T

heE

xcha

nge

Rat

eU

sed

byth

eS

yste

m

1Y

esY

esY

es

Ifth

em

anu

ale

xcha

nge

rate

isno

tze

ro:

The

curr

enc

yqu

otat

ion

met

hod

isch

eck

ed.

Ifth

equ

otat

ion

met

hod

isde

fine

da

sT

rian

gula

tion,

Cro

ssR

ate

as

The

Prim

ary

Vis

ualR

ate,

and

Do

Not

Allo

wC

ross

Ra

teO

verr

ide,

am

ess

age

app

ear

s,a

ndth

em

anua

llyen

tere

dex

cha

nge

rate

isig

nore

dby

the

syst

em

.Ara

tety

peis

requ

ired.

Ifth

eR

ate

Type

field

isbl

ank,

ane

rror

mes

sage

appe

ars,

and

the

Rat

eTy

pefie

ldtu

rns

red.

Ifth

ecu

rren

cyqu

otat

ion

isno

tsub

ject

toth

ea

bove

rest

rict

ion,

itre

trie

ves

the

syst

em

rate

.

Ifth

esy

ste

mra

teis

notz

ero,

itco

mpa

res

the

syst

em

rate

with

the

ma

nua

lrat

efo

rva

rianc

ech

ecki

ng.I

fthe

curr

enc

yqu

ota

tion

me

thod

isov

erm

axi

mum

vari

ance

and

the

err

orty

peis

sto

p,a

ne

rror

mes

sage

app

ear

s,a

ndth

eE

xcha

nge

Rat

efie

ldtu

rns

red.

Ifth

ecu

rren

cyqu

ota

tion

me

thod

isov

erm

axi

mum

varia

nce,

butt

hee

rror

type

iswa

rnin

g,a

wa

rnin

gm

essa

geap

pea

rs.T

heR

ate

Type

field

clea

rsa

ndth

em

anu

alra

teis

used

asth

eex

chan

gera

te.If

the

curr

ency

quot

atio

nm

etho

dis

noto

verm

axim

umva

rianc

ea

ndth

ere

isno

syst

em

rate

,the

ma

nua

lrat

eis

used

as

the

new

exc

hang

era

tean

dth

eR

ate

Type

field

cle

ars.

Ifth

em

anu

ale

xcha

nge

rate

isze

ro,i

tthe

syst

em

cle

ars

the

Rat

eTy

pefie

ldan

dus

es

zero

as

the

new

exc

hang

era

te.

2Y

esN

oY

es

Sa

me

as

scen

ario

num

ber1

.



Sce

nario

Cur

renc

yC

hang

ed?

Rat

eTy

peC

hang

ed?

Man

ual

Exc

hang

eR

ate

Cha

nged

?T

heE

xcha

nge

Rat

eU

sed

byth

eS

yste

m

3Y

esY

esN

o1.

Ifth

eR

ate

Type

field

isno

tbla

nk,t

hesy

ste

mus

esth

ene

wra

tety

peto

retr

ieve

the

new

syst

em

rate

and

uses

ita

sth

ene

wex

cha

nge

rate

.

2.If

the

Rat

eTy

pefie

ldis

blan

k,th

ene

wex

cha

nge

rate

isze

ro.

4Y

esN

oN

o1.

Ifth

eex

istin

gra

tety

peon

the

jour

nal

line

isno

tbla

nk,u

seit

tore

trie

veth

ene

wex

cha

nge

rate

.

2.If

the

exis

ting

rate

type

onth

elin

eis

blan

k,an

dif

the

exi

stin

gex

cha

nge

rate

onth

elin

eis

notz

ero,

use

the

exis

ting

exch

ang

era

te.I

fthe

exi

stin

ge

xcha

nge

rate

onth

elin

eis

zero

,the

exc

hang

era

teal

soeq

uals

zero

.

Ple

ase

note

that

,in

this

sce

nari

o,th

eex

cha

nge

rate

istr

eate

das

unch

ange

d.D

epe

ndin

gon

whe

the

rfor

eig

na

mou

ntan

d/or

mon

etar

yba

seam

ount

isch

ang

ed,t

heex

chan

gera

teca

nbe

reca

lcul

ate

d.S

eeth

ea

mou

ntch

ang

eru

les

form

ore

info

rmat

ion.

For

exam

ple

,if

you

cha

nge

the

fore

ign

curr

enc

y,fo

reig

na

mou

nt,a

ndm

onet

ary

base

amou

ntbu

tle

ave

the

rate

type

and

exch

ange

rate

as

is,t

hesy

ste

mre

calc

ula

tes

the

exch

ang

era

teba

sed

onth

ene

wfo

reig

nam

ount

and

mon

etar

yba

sea

mou

nt.

5N

oY

esY

es

Sa

me

as

scen

ario

num

ber1

.

6N

oN

oY

es

Sa

me

as

scen

ario

num

ber1

.



Sce

nario

Cur

renc

yC

hang

ed?

Rat

eTy

peC

hang

ed?

Man

ual

Exc

hang

eR

ate

Cha

nged

?T

heE

xcha

nge

Rat

eU

sed

byth

eS

yste

m

7N

oY

esN

oS

am

ea

ssc

ena

rionu

mbe

r3.

8N

oN

oN

oW

hen

the

exc

hang

era

teis

unch

ange

d,th

esy

ste

mus

es

the

prio

rexc

hang

era

te.



Calculating Using the Calculate RulesThe calculate value determines how and which of the foreign amount, exchange rate, and base amountfields are calculated for the line item. The default calculation rule issystem rule.

If the values generated for foreign amount, exchange rate, or base amount by thesystem rulearedifferent from those you want, you can change them using other calculate rules.

When you change any of these values, you must be aware of the possible actions and select the correctcalculate value to achieve your proposed change. For example, if you want to change the foreign amount andnot the base amount, but expect the system to calculate and change the exchange rate to result in the originalbase amount, the system rule will not calculate the exchange rate but will calculate the base amount.

Note. Changedmeans the new value is different from the prior value. The new value can bezero or non-zero. The prior value can also be zero or non-zero. If you change a field to a newvalue but then change it back to the prior value before you initiate the calculation process, thefield is treated as unchanged. The system tracks changes by comparing the prior value stored inthe buffer with the new value when the calculation process is initiated.

The calculate rules and their actions are as follows:

System Rule This is the default value and uses the following rules to calculate values:

• When two of the three values are changed, the unchanged value is calculated.

• When only the foreign amount is changed, and if the exchange rateis not zero, the base amount is calculated.

If the exchange rate is zero, the exchange rate is calculated.

• When only the base amount is changed, and if the exchange rate isnot zero, the foreign amount is calculated.

If the exchange rate is zero, the exchange rate is calculated.

• When only the exchange rate is changed, and if foreign amount isnot zero, the base amount is calculated.

If foreign amount is zero, the foreign amount is calculated.

• When you change all three values, make sure the values are correct.

The system calculates the base amount and compares it with the baseamount you entered. If they are unequal and if none of the three valuesis zero, an error message appears, and you must correct the values. Ifone of the three values is zero, its value is calculated.

Amount Calculates the foreign amount when you provide the exchangerate and base amount.

Base Amount Calculates the base amount when you provide the foreignamount and exchange rate.

Exchange Rate Calculates the exchange rate when you provide the foreignamount and the base amount.



You can use the Journal Entry template to make the Calculate field unavailable just as youcan other fields. For example, you can define a base currency journal entry template thatcan be used for entering base currency lines only.

Checking When the Exchange Rate is Calculated

The exchange rate is calculated based on the foreign amount and monetary baseamount when the following are true:

• The Calculate field value each journal line that is set toExchange Rate.

• The Calculate field value on each journal line is set toSystem Rule, and both theforeign amount and monetary base amount change.

• The Calculate field value on each journal line is set toSystem Rule, the foreign amount (or monetarybase amount) changes, the exchange rate doesn’t change, and the exchange rate value is zero.

• The Calculate field value on each journal line is set toSystem Rule; the foreign amount, monetarybase amount, and exchange rate all change; the monetary base amount is not equal to foreignamount multiplied by exchange rate; and the exchange rate value is zero.

The system also performs two exchange rate tests, it:

• Checks the currency quotation method.

If it is defined as Triangulation, Cross Rate as the Primary Visual Rate, and Do Not Allow Cross RateOverride, a system rate must be used because the exchange rate cannot be calculated.

• Checks the variance between the system rate and the calculated exchange rate to see if it’s over tolerance.

The calculated exchange rate cannot exceed the tolerance if the error type isstop.

Note. The Journal Entry process uses deferred processing, which reduces the number oftrips to the server. For example, when you enter a department ID, the system won’t validateyour entry until the next trip to the server is requested.

Open Item Key The field is only required in the case of open item transactions, such asdeposit accounts or employee draw accounts. In such cases, you would enterthe open item key against which the journal line is applied. For example,suppose US001 has an open item account for employee advances, wherethe open item key is the employee’s social security number. When youdebit or credit this account, you would be required to enter the appropriateemployee social security number in the open item key field. In this way,journal lines containing open item transactions are matched to the individualopen items being tracked within PeopleSoft General Ledger.

This field is available unless you exclude it from the journal line using theJournal Entry Template. If you enter an open item account, you must alsoenter an open item key or you’ll receive an error message when you save.Also, if you enter an open item key for an account that is not an openitem account, you’ll receive an error message when you save.

Suspended Line This column is used to reference the edit (or amount) suspense line tothe line in error (Line 1) and vice versa. The Suspended Line column isalways be equal to its journal line for balance suspense lines.



Budget Date Enter the date used to determine the budget period of the control budgetif you use the commitment control option. The budget date valuedefaults to the journal date, but you can override it.

Reference The field enables you to refer each line back to a document, person,invoice, date, or any other piece of information that helps youtrack the source of the transaction.

Journal Line Description Displays the description defined for the account ChartField value; youcan change this to better describe the transaction. The descriptionappears in prompt lists for this journal line.

VAT When you click this link, an error message appears if the account is a non-VATaccount or VAT processing is not applicable. You can use the Journal EntryTemplate to make the VAT link unavailable or on journal lines.

Note. The Journal Entry process uses the columns selected in the Journal Entry template to display the valuesin the line scroll area. If any columns listed above do not appear in your journal line, it’s likely that thesecolumns are not selected in your Journal Entry template. You must modify your Journal Entry template toselect these columns or choose another Journal Entry template that has these columns selected.

Totals

To aid in balancing the journal, a running total of the number of lines, the total debits, totalcredits, journal status, and budget status of the journal appear at the bottom of the Journal Entry- Lines page. Only balanced entries can post to balanced ledgers.

Journal Status If the journal contains errors, you can click the status to go directly to theJournal Entry − Error page. The cursor is positioned on the journal header error.

D: Deleted − Anchor Journal Unposted

I: Posting Incomplete − Repost ASAP

M: Valid SJE Model − Do not Post

E: Journal has Errors

N: No Status − Needs to be Edited

P: Posted to Ledger(s)

T: Journal Entry Incomplete

U: Unposted

V: Valid journal − Edits completed

Z: Upgrade Journal − Can’t Unpost

Budget Status Click on this link if the budget status isError or Valid (with warning), toaccess the Commitment Control page, where you can see the error or warningmessages. You can also flag the journal to make it pass budget checking, eventhough it exceeds the budgeted amount. Possible values are:

• E - The entry failed to pass budget checking

• N - The Budget Processor has not processed the entry.



• V - The entry passed budget checking with or without warningsand the control budget has been updated.

See Also


Selecting a Journal Entry TemplateAccess the Journal Entry Template List page.

Journal Entry Template List page: ChartField tab (1 of 2)

Journal Entry Template List page: ChartField tab (2 of 2)

Select the template that defines which columns appear in the lines scroll area. Also specify the fieldvalues to be copied down to new lines when you click the Insert Journal Lines button

ChartField Tab

Click the ChartField tab.

Note. If a particular ChartField column is selected, it won’t necessarily appear on the journalline grid. It appears only if the column is selected and it is one of the ChartFields for the currentjournal’s ledger. For example, ifscenariois not a ChartField for the current journal’s ledger, it won’tbe shown on the journal line grid even if it’s selected on the template.

Selected Indicates the template you are currently using. This is the only field you canselect on the Journal Entry Template − Show Journal Line Grid Columns page.

Template Type Identifies who would use the template. For example, anyonecould use anAll template type.

Template ID The name for the template.



Default This check box is selected if the template was designated as the defaulttemplate on the Journal Entry Template − Template page. You can change thedefault only on the Journal Entry Template − Template page.

Note. If you want to change a template definition, you must do so on the Journal Entry Templatepage under Set Up Financials/Supply Chain, Common Definitions, Journals.

Amount Tab

Click the Amount tab.

Journal Entry Template List page: Amount tab

Select the journal line columns that pertain to the journal line amounts.

Miscellaneous Tab

Click the Miscellaneous tab.

Journal Entry Template List - Miscellaneous page

Select the miscellaneous columns for the journal entry template. These columns appear on your journal lines.

Note. Even if the Budget Date check box is selected, it won’t necessarily appear as a column on the journalline grid. It appears only if you select it hereand the current journal line has the Commitment Control processenabled. Similarly, if you select the VAT column here, it appears as a column on the journal line grid only ifyou select it hereand the business unit of the current journal line has the VAT process enabled.

See Also




Setting Journal Entry Copy Down OptionsThe Journal Line Copy Down settings for templates appear on the same page as the Show JournalLine Grid template. They also have the same tabs and the same toggle buttons to show all columnsand to show tabs as described for the Show Journal Line Grid page.

Journal Entry Template List - Journal Line Copy Down - ChartField tab (1 of 2).

Journal Entry Template List - Journal Line Copy Down - ChartField tab (2 of 2).

When you add a journal line on the Lines page, the fields you selected on the Journal Entry Template− Journal Line Copy Down page are copied from the preceding line.

You define a variety of copy down templates on the Journal Entry Template page. These pre-definedtemplates load for your selection when you enter journals. For example, you can define one templateto copy down all fields and another to copy down all fields except the amount fields.

Note. You can temporarily change your copy down selections on the Journal Line Copy Down pagefor the current journal. However, these changes are ignored after you exit the current journal. If youwant to save the changes, you must do so on the Journal Entry Template page, which is accessedunder Set Up Financials/Supply Chain, Common Definitions, Journals.

Default is selected if the template was designated as the default template on the JournalEntry Template − Template page.

Entering Projects InformationAccess the Projects Information page.

PC Business Unit(PeopleSoft Project Costbusiness unit)

Business unit assigned to the project in PeopleSoft Projects.

Project The project ID assigned to a project. The project must already beestablished in PeopleSoft Projects.

Activity ID (identification) The activity ID assigned to the individual tasks or events thatyou want to update in a project.



Resource Type The resource category, such as labor, associated with a givencost. Used in conjunction with resource category, resourcesubcategories, and resource groups.

Resource Category (Optional) Used to specifically refine resource types, similar to the relationshipbetween entry type and entry reason in PeopleSoft Receivables. For example,if you have a resource type of labor but want to break it down furtherfor tracking purposes, you might define resource categories of architecthours, carpenter hours, plumber hours, and electrician hours.

Resource SubCategory (Optional) Used to refine resource categories. For example, if youhave a resource type of labor and resource categories of architecthours, carpenter hours, and plumber hours, you might want resourcesubcategories of regular hours and overtime hours. .

Resource Analysis Type A three-character, user-definable identifier that enables you to label thedifferent types of costs in PeopleSoft Projects. For example, you might want totrack budgeted costs (BUD), committed costs (COM), and actual costs (ACT).

Accessing the Secondary Ledger LinesAccess the Secondary Ledger Lines Page.

Viewing Secondary Ledger Lines

Note. This page or related pages operate in deferred processing mode. Most fields are not updated or validateduntil you save the page, refresh it by clicking a button or link, or select tab. This delayed processing hasvarious implications for the field values on the page. For example, if a field contains a default value, any valueyou enter before the system updates the page overrides the default. Another implication to keep in mind is thatthe system updates quantity balances or totals only when you save or click the Calculate Amount button.

Secondary Ledger Lines The page displays the secondary ledger for the journal lines when they exist,as well as the other journal details. When you enter a primary journal line,the system automatically populates the secondary journal line’s rate type,retrieves the exchange rate, and calculates the base amount.

The Rate Type This field is populated in the following order:

• Rate type defined on the Ledger Group - Definition page.

• Rate type entered for the primary journal line.

• Default rate type defined on the Ledger Group − Definition page.

Rate Type, Exchange Rate,or Base Amount

You can override the values in the fields. When you are done, click theBack to Primary Lines button next to the secondary ledger field The cursoris positioned at the primary line of the secondary ledger.



The Calculate Amount button is available from the Secondary Journal Linespage, and the process is similar to the calculation on the Journal Lines page;however, the foreign amount cannot be changed from the secondary page.

Back to Primary Lines Click to return to the Journal Entry − Lines page.

Note. Before making changes to the secondary lines, carefully review the calculate rules, options, andrequirements for various changes that are detailed in the documentation for the journal Lines page.

Using Statistics CodesStatistics codes, like statistical accounts, are used to identify non-monetary amounts. They areassociated with a specific unit of measure. If you want to enter a statistical amount on the samejournal line with a related monetary amount, you can select a statistics code in the Stat (statistics)field on the Lines page. When you select a statistics code, also enter the Statistical Amount for aunit and the corresponding UOM (unit of measure) for that statistics code.

Because all statistical and monetary fields are potentially available on the journal line depending onyour selection of templates, error messages may appear during the save process when you have enteredinconsistent data. Error messages are issued if any of the following occurs:

• The account is a statistical account, but the statistic code, foreign amount, monetary amount,foreign currency, rate type, or exchange rate is not blank

• The account is a statistical account, but the statistic amount is blank

• The account is a monetary account and the statistic code is blank, but the statistic amount is not blank

When you receive an error message, the cursor moves to the error field of the journal line inerror. If the field was originally unavailable because of the journal entry template definition,the column is shown so that the cursor can be positioned.

See Also


Chapter 21, “Using Commitment Control in PeopleSoft General Ledger,” page 449

Chapter 11, “Using Open Item Accounting,” page 223

Chapter 4, “Using Statistics,” page 37

Specifying Journal Entry TotalsAccess the Journal Entry − Totals page.



Journal Entry − Totals page

Note. This page or related pages operate in deferred processing mode. Most fields aren’t updated or validateduntil you save the page, refresh the page by clicking a button or link, or select a tab. This delayed processinghas various implications for the field values on the page—for example, if a field contains a default value, anyvalue you enter before the system updates the page overrides the default. Another implication to keep in mindis that the system updates quantity balances or totals only when you save or otherwise refresh the page.

Control Totals Specify the total debits, credits, statistical units, and number of lines to beentered for each unique combination of business unit, ledger, transactioncurrency, and additional balancing ChartFields (like book code and balancesheet indicator if they are set to active at Installation Options — Overall page,and so on). As you enter the journal lines, the system displays a running total ofthe actual debits, credits, units, and lines, as well as the net difference betweenthe amounts entered and the control totals. If you leave any of the control totalfields blank, the system won’t validate against the associated actual total.

For example, suppose you have plans to allocate rent expense across severaldepartments and know that the total rent expense is 50,000 USD for 2,000square feet. Because you know how many departments are involved, youknow that there will be 15 lines in the completed journal entry. You enterthese amounts as control tables to ensure that when one of your staff membersenters the journal lines, these figures match before the journal is posted.

Control totals are maintained by business unit, balancing ledger,balancing ChartFields (if any), and currency code. If you enter aninterunit journal, for example, the system maintains a set of controltotals for each business unit. Also, if additional balancing ChartFieldsare defined, the system maintains a separate set of control totals foreach unique combination of the ChartFields entered.

Actual Totals When the journal lines are entered, the system calculates the actual totaland compares it against any control totals entered.



Difference When the journal lines are entered, the system calculates theactual total and compares it against any control totals entered andnotes any differences in amounts.

When you edit the journal and the control totals don’t equal theactual totals, the system flags the journal as having errors, and youmust correct the errors before you can post.

Note. Refresh the page after any changes.

See Also


Viewing Journal Entry ErrorsAccess the Journal Entry - Errors page.

Journal Entry − Errors page

You can view journal entry errors on the Journal Entry - Errors page by clicking theX in the Errorcolumn on the Journal Entry - Lines page. When PeopleSoft General Ledger encounters errors duringediting, it marks the journal lines and either recycles or suspends the journal. It saves recycled journalsbut won’t post them until you correct the errors. You can post entries to your suspense account thathave invalid ChartFields, different signs on the transaction and base amount, or unbalanced debit andcredit amounts. You define error-processing options at the business unit, ledger group, and journal sourcelevel. Move to the Journal Entry - Errors page to determine which errors the system encountered. Whenyou’re done, click the line number in error. This moves you to the Journal Entry − Lines page. Thecursor is positioned on the line and field in error so that you can make corrections.

Note. This page or related pages operate in deferred processing mode. Most fields will not be updated orvalidated until you save the page or refresh it by clicking a button, link, or tab. This delayed processing hasvarious implications for the field values on the page. For example, if a field contains a default value, any valueyou enter before the system updates the page will override the default. Another implication to keep in mind isthat the system updates quantity balances or totals only when you save or otherwise refresh the page.

Field Name Shows the field in error, as well as message sets that contain the errormessage, message number, and message text.

Unit Click to open the Journal Entry − Lines page and position the cursorin the Journal Status of the Totals scroll area.



Line # Click to open the Journal Entry − Lines page and position the cursorin the line and field with the error.

See Also

Chapter 10, “Processing Journals,” Journal Error Processing, page 195

Specifying Journal Entry Approval OptionsAccess the Journal Entry - Approval page.

Journal Entry − Approval page

Note. This page or related pages operate in deferred processing mode. Most fields will not be updated orvalidated until you save the page or refresh it by clicking a button, link, or tab. This delayed processing hasvarious implications for the field values on the page. For example, if a field contains a default value, any valueyou enter before the system updates the page will override the default. Another implication to keep in mind isthat the system updates quantity balances or totals only when you save or otherwise refresh the page.



Approval Status

The Approval Check Active field indicates whether there is an approval workflowprocess required for the journal.

This page displays the current approval status:

Denied Journal is denied.

Pending Approval Journal is waiting for approval.

Approved to Post Journal is approved.

None Not applicable.

In the Approval Action drop-down list box, select the appropriate action for this journal:

Approve Journal is approved for posting. If you have the authority to approve thejournal, the system saves it as usual. If you don’t have the authority, youare prompted to enter the journal into PeopleSoft Workflow.

Deny Journal is not approved for posting. If you change the action to deny, thesystem sends an email to the previous user with a list of the journal identifiersand the reasons entered in the Comments for Denial Email field.

Recycle Journal is neither approved nor denied. The system creates awork list entry for the previous user.

The Comments for Denial Email field contains the reason for the denial.

Approval History

The Approval History group box lists the step and path, with the status and applicable date/timestamp and user ID for the various activities in the approval process.

See Also

Chapter 22, “Approving Journal Entry,” page 465

Creating Inter/Intraunit Journal EntriesThis section discusses how to:

• Set up for inter/intraunit journal entries.

• Create intraunit journal entries.

• Create interunit journal entries.



Pages Used to Make Inter/Intraunit Journal Entries


Ledger Groups − BalancingLEDGER_GROUP3 General Ledger, Ledgers,Ledger Groups, Balancing

Elect to use intraunitbalancing entries and selectbalancing ChartFields andaffiliates for a ledger group.

Create Journal Entries− Lines

JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries

Enter journal lines andrecord inter/intraunittransactions.

Setting Up for Inter/Intraunit Journal EntriesAccess the Ledger Groups - Balancing page.

Ledger Groups - Balancing page

IntraUnit BalancingEntries

Unless you click this check box, inter/intraunit processing does not createintraunit balancing entries for balancing ChartFields, such as fund, evenif different fund values appear in the same journal.



Balance Click to select balancing ChartFields. A ChartField must be selected to fullyuse the anchor and grouping options when creating intraunit journal entries.

Creating Intraunit Journal Entries.Access the Create Journal Entries - Lines page.

Create Journal Entries - Lines page

Inter/IntraUnit Groups

If you select additional balancing ChartFields beyond those delivered as balancing ChartFields, thoseChartFields appear in the Inter/IntraUnit Groups area. In this example, Fund has been selected asan additional balancing ChartField on the Ledger Groups - Balancing page.

An entry can be both interunit and intraunit, but multiple anchor is available only for the intraunit portionof that entry. The business unit on the journal header is the anchor unit for interunit journal entries.

Inter/IntraUnit Click button display the Inter/IntraUnit Groups group box to assigninter/intraunit groups and anchors for intraunit entries when youhave additional balancing ChartFields.

IU Group Displays the balancing ChartField columns if IntraUnit Balancing Entriesis selected on the Ledger Group - Balancing page. It does not displaybusiness unit, book code, and adjustment type.



Initially all journal entry lines are assigned to an inter/intraunit group of1.

Click the Add multiple rows button to add new inter/intraunit groups rows.

Newly added inter/intraunit groups rows have zero journal entry linesassigned. To assign lines enter the row to which you want to add lines.Select the journal entry line or lines in the journal entry Lines area ofthe page by selecting the Select check box.

After selecting the option and lines as described above, click theInter/IntraUnit button again. This makes all journal lines selected membersof the inter/intraunit group, which also has its option selected.

The ChartField values you enter in the inter/intraunit groups are theanchors for their respective intraunit groups. For example, if withinbusiness unit FED01, cash from fund F510 is used to pay expensesattributable to funds F100 and F133, fund F510 can be designated theanchor for that group of intraunit transactions.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Using Interunit and IntraunitAccounting and ChartField Inheritance,” Anchor Entity

Creating Interunit Journal EntriesFor interunit journal entries, the anchor is the business unit entered on the Header page. You can add additionalinter/intraunit groups, but the business unit entered on the journal header remains the anchor.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Using Interunit and IntraunitAccounting and ChartField Inheritance,” Using ChartField Inheritance

Chapter 12, “Using Inter/Intraunit Processing in PeopleSoft General Ledger,” page 233

Posting to Summary Ledgers and the SummaryLedger Staging Table

You can update your summary ledgers at the same time you post changes to the detail ledgers as partof the posting process by selecting the Post to Summary Ledgers check box on the Ledger Set page.The journal post calls the Summary Ledger process (GLPSMAIN) at the end of processing for eachbusiness unit, passing the business unit and the staging table name. The staging table is basicallya copy of the ledger table. The Journal Post process populates this table.

The summary ledger compares the rows in the staging table with the rows in the status table to determinewhich ledgers to increment. It then compares those with the ledger set definition to see if the increment isallowed. Summary ledgers that have not yet been created when called from the Posting process are not created.



Note. To run an incremental summary ledger request, you must create a particular summary ledger/accountingperiod before it can be incremented through posting. Once you run the request, the rows in the staging table arecompared with those in the status table so that the system can determine which ledgers to increment.

See Also

Chapter 18, “Reviewing Financial Information,” Viewing Journal Information, page 395

Creating SJEsThis section provides an overview of SJEs and discusses how to:

• Define SJEs.

• Set up schedules.

• Create a standard journal entry.

• View the status of standard journal entries.

• View the amount spread.

• Run the standard journal entry process.

Understanding SJEsWith SJEs, you can automate the entry of similar or identical journals. You can definethree types of standard journal entries:

• Recurring: Use Recurring journal entries for repetitive transactions that use the sameaccounting information and amounts.

Monthly rent, automobile lease payments, and amortization expenses are examples of recurring items forwhich you might charge constant amounts to the same ChartField combinations each period.

• Template: Use Template journal entries for regular, periodic transactions that you charge tothe same ChartField combinations using varying amounts.

Examples include monthly payroll, utility, and telephone expenses. You can schedule regular, recurringpostings for standard journals, such as weekly postings, or schedule postings for selected dates.

You can schedule journal entries automatically on predetermined dates using template SJEs.Examples include bonus payments and accrued interest. You can also create template SJEs forknown ChartField combinations without specific dates or schedules. You can set up schedulesthat determine when SJEs post, and you can enter recurring schedules, such as weekly closings,or individual dates and times to help pinpoint specific events.

• Spread: Use Spread journal entries for transactions for which the entire cost is spreadproportionately throughout the year.



Pages Used for Creating SJEs


Define Standard Journals SJE_STNDRD_JRNL General Ledger, Journals,Standard Journals, DefineStandard Journals

Create a standard journalentry. Enter a StandardJournal ID that becomesthe high-level key for alljournal entries generatedusing this definition.

Standard Journals SJE_JRNL_INQ General Ledger, Journals,Standard Journals, ReviewStandard Journals

View the status of a standardjournal entry.

Control Totals SJE_TOTALS_SEC On the Standard Journalspage, click Remaining.

View the total amount andremaining amounts ofdebits or credits of a spreadSJE type.

Standard Journal Batch(Application Engine)

SJE_BATCH_REQ General Ledger, Journals,Standard Journals, CreateStandard Journals

Run the SJE process(GL_SJE) to create standardjournals.

Defining SJEsBefore you can define recurring, template, or spread journals, you must first create model journalentries using the Journal Entry pages. The SJEs and their models must be from the same businessunit. The following illustration outlines the steps required to set up SJEs:



SJE Process



Setting Up SchedulesRecurring journal entries require processing schedules. In PeopleSoft General Ledger, you can createschedules that automate and control the generation of standard or recurring journal entries. You candefine daily, weekly, monthly, or annual schedules for recurring transactions such as closing schedules,or you can schedule specific user-defined events such as expense report due dates.

Schedules control the frequency of processing. For example, if you pay your rent on the 15th ofeach month, select a monthly schedule that specifies the day of the month as the 15th. By definingschedules that are tailored to your accounting environment, you can easily automate the creation ofan SJE or a group of SJEs. You can set up daily, weekly, monthly, annual, or user-defined schedules.User-defined schedules enable you to specify particular dates and times.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and SupplyChain Management Common Definitions,” Setting Up Schedules

Creating a SJEAccess the Standard Journal Definition page.

Define Standard Journals page

SJE ID (standard journalentry identification)

The standard journal entry (SJE) identification value. Use the longdescription field to the right to describe this SJE.



Seq Nbr (sequence number) Identifies the number of the SJE detail. The next field is a descriptionof this detail. One SJE may have multiple SJE details.

SJE Type (standard journalentry type)

Enter a description of the SJE.

Template: PeopleSoft General Ledger uses a template as a data entry modelfor other journal entries. You can automatically reproduce it on a fixedschedule like recurring SJEs, or you can use it on request. When you definethe template, specify whether you want the ChartField values copied fromthe model to the generated journal entry. Examples of templates are monthlypayments with different amounts such as telephone and utilities.

Recurring:A recurring journal entry is any entry that should be automaticallyrecorded in its entirety according to a fixed schedule. These entriescontain the same ChartField values and amounts, such as monthly rent,lease payments, and depreciation expense.

Spread:In a spread journal entry, the total amount is spread proportionatelyacross all the periods. For example: a company charges you a flatfee of USD 10,000 annually to perform a service. You could dividethat amount by 12 and create recurring entries for the same amounteach month (USD 10,000/12=833.33).

Status One of the following appears:

Active: When you first create an SJE, its status is active. The SJEmay have more journals to be created.

Error: This status signifies that the last time the Standard Journalprocess attempted to process this SJE, an error occurred. The SJEcontinues to show a status of error until the next time the batch processis run after the problem causing it is fixed.

Completed:All the standard journals for this SJE have been created. A SJEwith a status of completed may still be modified. To do this, reactivatethe SJE and extend the range of dates or periods.

Model Journal In this group box, specify the model journal for the SJE. This modeljournal must belong to the same unit as the SJE. Once you select yourjournal and date, the model journal status appears. Your model journalmust conform to the following requirements:

• It must have a status ofSJE Modelif it is a spread SJE.

• It must have a status ofSJE Model, Valid,or Postedif it isa template or recurring SJE.

Standard Journal In this group box, enter the journal ID for the SJE. Also enter the documenttype that you used for document sequencing for the standard journals.

Document Type Identify the document type.

Allow Lines to be Modified This check box controls whether the standard journals can be modifiedbefore being posted using the Journal Entry page. Clear this check boxif you want to prevent standard journals from being modified.




Click to enable you to save this journal as incomplete.

Create Standard Journals In this group box, specify the sequence of dates of the standardjournals to be created.

Schedule If the SJE type that you specified is eitherTemplateor Recurring,theSchedule field appears, enabling you to enter the frequency of your SJEs.In the From Date and To Date fields, enter the range of your SJEs.

From Year/Period andToYear/Period

If your SJE type is spread, designate the range of periods in these fields.

Journal Day in CalendarPeriod

Enter the day to establish a journal date for the Standard Journals. Forexample, when you enter 20 in this field, you indicate to the systemthat you want the journal date of the standard journals to be the 20thday of each period. This designates the journal date only, not the dateon which the system creates the standard journal.

Journal Creation LeadDays

Enables you to create standard journals in advance. Enter the numberof days in advance of the journal date that you want the standard journalsto be ready for creation. If you leave this field blank, the systemcreates the standard journals on the journal date.

If you must change the details, such as ChartFields, dollar amounts, orstatistical amounts on standard journals, use one of these two options:

• Open the SJE in the Standard Journal page and select adifferent model journal.

• Open the model journal in the Journal Entry page and modify it as necessary,provided it has not yet been posted. No change to the SJE itself is necessary.

Standard Journals Created This scroll area shows the SJEs and their statuses.

See Also


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and SupplyChain Management Common Definitions,” Setting Up Schedules

Viewing the Statuses of Standard JournalsAccess the Review Standard Journals page.



Review Standard Journals page

Viewing the Amount SpreadAccess the Control Totals page.

Standard Journal Entry Totals page

Total The amount spread in this journal.

Remaining The amount yet to be spread.

Running the Standard Journal Entry ProcessAccess the Create Standard Journals Request page.

Create Standard Journals Request page



From SJE andTo SJE Select the from and to SJEs for this request. If these fields are blank, thesystem processes all SJEs in the designated business unit. For example, ifyou want to run journals for all valid SJEs for business unit US001, enterthe business unit and leave the SJE from and to values blank.

Delete Journals This check box enables you to regenerate standard journals. If this checkbox is selected, the system deletes any standard journals created by anSJE that is not posted and has not been budget checked.

Recalculate Budget Date If this check box is selected, the SJE process sets the budget date as thejournal date; otherwise, it copies the old budget date.

Note. You must run Journal Edit after processing standard journal entries in order to obtain the correct journal ID.

Editing Journal EntriesWhen you edit a journal entry, PeopleSoft General Ledger runs several checks and warns you if the journalentry cannot be posted. A journal entry cannot be posted if one or more of the following conditions are true:

• The accounting period (determined by the journal date) is not currently open.

• Total debits do not equal total credits, and the ledger is defined as a balanced ledger.

• Any control totals entered with the journal header do not match the actual totals for thejournal (debits, credits, statistical units, number of lines).

• One or more journal lines use inactive or invalid ChartFields as of the journal date.

See Also

Chapter 10, “Processing Journals,” Requesting Journal Edits, page 200

Copying Journal EntriesThis section provides an overview and discusses how to:

• Run the copy journals process.

• Define copy journal dates.

• Copy journals online.

Understanding Copying JournalsYou might find that similar or identical journals recur with some frequency. To avoid having to retype thesame information, you can use an existing journal as the basis for a new journal entry. Do this using the CopyJournal page for the batch process or you can also use the Copy Journal Entry page to make an online copy.

You can copy posted or unposted journals and then change the header or detail lines, as desired. Thecopied journal must have a new journal number. You can specify the following:



Note. Journal Copy does not copy system created lines, which are normally recreated when yourun an edit against a journal. So, if you copy an interunit journal with the reverse amount option,the interunit lines of the newly copied journal will be created according to interunit accounts ofthe resulting copied journal. If you want to completely reverse a previous journal, use the reversaloption on the journal before it is posted, or unpost it if it is already posted.

Date You can copy to either a new journal date or a new ADB (average dailybalance) date (if the associated ledger group supports ADB reporting).

Ledger In order to be able to copy a journal to another ledger, both ledgersmust be in the same ledger group and the Keep Ledgers in Syncoption shouldnot be enabled.

Document type This field is available only if you have enabled documentsequencing for your system.

Additionally, you can create reversals for the copied journal regardless of whether the originaljournal had reversals. And you can change the signs of the copied journal.

Pages Used to Copy Journals


Copy Journals Request JOURNAL_COPY_REQ General Ledger, Journals,Journal Entry, Copy Journals,Copy Journals Request

Run the CopyJournal process.(GL_JRNL_COPY).

GL Copy Journal ProcessingCOPY_JOURNAL_REV On the Copy JournalsRequest page, click Reversal.

Define how the systemdetermines the journal dateand the ADB date for thereversal journals associatedwith a copied journal.

Journal Entry Copy JOURNAL_ENTRY_COPY General Ledger, Journals,Journal Entry, Create JournalEntries, Lines

Select Copy Journals inProcess field and clickProcess button on the JournalLines page.

Use to copy a journalonline.This is an online feature inaddition to running the copyjournal process.

Running the Copy Journals ProcessAccess the Copy Journals Request page.



Copy Journals Request page (1 of 2)

Copy Journals Request page (2 of 2)

Language Select the language in which you want your report printed.

Unit, Journal ID, andDate Enter the information to identify the journal you want to copy.

ADB Date (average dailybalance date)

If your journal is for a ledger group that supports ADB reporting,enter the ADB date.

New Journal Enter a specific journal ID or useNEXT in this field to automaticallyassign the next journal number to the new journal.

New Date Enter a journal date for this new journal. The default is the current system date.

New ADB Date Enter the ADB date for the new journal, if it is different from the journal date.

Ledger If the journal is for a ledger group that contains multiple ledgersand doesnot have the Keep Ledgers in Sync option enabled, theLedger column appears. Enter the ledger.

New Ledger This field appears if the original journal is associated with a ledgergroup that contains multiple ledgers and doesnot have KeepLedgers in Sync option enabled.

Reversal Click this link to open the GL Copy Journal Processing page,where you can specify processing options for the journal date andthe ADB date for the reversal.

Document Type Select a document type only if you’ve enabled document sequencingfor your system. If document sequencing is enabled and you leave theDocument Type field blank, the system copies the document type from theoriginal journal. Several journal entry reports and inquiries allow youto search for journals by document sequence number.

Reverse Signs Select this if you want the new journal to have the oppositesign from the original journal.

The new journal will be marked with a status of Not Yet Edited, andyou must edit it before it can be posted. As a rule, editing a journalexecutes the validation process required for posting.



Recalculate Budget Date If selected, the SJE process sets the budget date as the journal date;otherwise, it copies the old budget date.


If selected, the new journal saves in an incomplete status.

Note. You must run Journal Edit after running the Copy Journals process to obtain the correct journal ID.

Defining Copy Journal DatesAccess the GL Copy Journal Processing page.

GL Copy Journal Processing Page

Reversal Date Select the appropriate reversal option.

Do Not Generate Reversal Assumes no automatic reversal of this entry. This is the default.

Beginning of Next Period Creates a reversing entry dated the first business day of the nextaccounting period. The system uses the business calendar that youassigned to the business unit on the General Ledger Definition −Definition page to determine the first business day.

End of Next Period Creates a reversing entry dated the last business day of the nextaccounting period. The system uses the business calendar that youassigned to the business unit on the General Ledger Definition −Definition page to determine the last business day.



Next Day Creates a reversing entry dated the next business day. The system uses thebusiness calendar that you assigned to the business unit on the General LedgerDefinition − Definition page to determine the next business day.

Adjustment Period Enables you to select the adjustment period for which the newjournal is to be created.

On Date Specified By User Enables you to select any date in the calendar of the target (posting) ledger.When you select this option, the system makes available the ReversalDate edit box for you to enter the appropriate date.

ADB Reversal Date If this reversal is for an average daily balance, select theappropriate reversal option.

Same as Journal Reversal Creates an ADB reversal with the same date as the one selected under Reversal.

On Date Specified by User Lets you select any date in the detail calendar of the ADB ledger (the ledgerthat stores the daily balances). When you select this option, the system makesavailable the ADB Reversal Date edit box for you to enter the appropriate date.

Note. Reversals are marked valid and ready to post when created; they do not need to be edited.When the journal date falls within the journal dates, fiscal year, and open periods specified on theJournal Post page, the system posts reversals as soon as they are created.

Note. You can also copy a journal by selectingCopy Journalin the Process field on the Journal Entry-Linespage. Click Process, and the system prompts you with a message before copying the journal.

Copying Journals OnlineAccess the Journal Entry Copy page.

Journal Entry Copy page

You can copy journals online using this page rather than using the copy journal batch process.



Open the journal that you want to copy. Access the Journal Entry Copy online page from the Journal EntryLines page by enteringCopy Journalin the Process field and clicking the Process button.

Use the field descriptions provided for the pages used in the batch process to understand andcomplete the fields on the Journal Entry Copy online page.

When you have completed entering any changes necessary for the new copy of the journal using the JournalEntry Copy online page, click the OK button and the system creates the new copy of the journal.

Deleting Journal Entries Not Yet PostedTo delete a journal, selectDelete Journalin the Process field on the Journal Entry − Lines page andclick Process. The system prompts you with a message before deleting the journal.

Note. You can delete only journals that have not yet been posted. The system makes no audittrail of the deletion because it assumes you are correcting a mistake.

You can delete a journal that has not been posted.

If the journal has been budget checked, one of several things can happen:

• You can delete a journal that is not yet posted after it successfully passes budget checking.

Delete it by navigating to the Journal Lines page, Process field, and choose the option toDelete Journal.This process calls the budget checking module, which reverses the budget entries.

• Depending upon the budget setup, the budget checking process runs before the journal is deleted.

If deleting the journal violates the budget checking rules, the journal fails budgetchecking and cannot be deleted.

• If an error occurs during the budget checking process (for example, budget on holdor closed), the journal isn’t deleted.

Note. You can alsounpostjournal entries that have been posted. This is a distinct process from deletingjournals that have never been posted and is described in the Processing Journals chapter.

See Also

Chapter 10, “Processing Journals,” Unposting Journals, page 209

Using the Journal Entry Import ProcessThis section provides an overview of the flat file format in the Flat File JournalImport process and discusses how to:

• Set up for file import.

• Import journal entries from flat files.



Understanding File Format in the Flat File Journal Import ProcessThe file format is determined by the File Layout Object (GL_JRNL_IMPORT). The following is the fileformat for the Flat File Journal Import process. PeopleSoft delivered a sample flat file named journal.dat underthe “data” folder. The layout varies depending on the first column with the following meaning:

# = Comments.

H = Journal header.

L = Journal line.

V = Journal VAT line.

C = Journal control totals.

Comments

This information describes the flat file’s comments format.

Column Length Description

1 1 #

2 100 Comments

File Format for Journal Header

This information describes the flat file’s journal header format.


1 1 H

2 5 Business Unit

7 10 Journal ID

A value of NEXT or blank createauto-numbered journal IDs.

17 8 Journal Date (MMDDYYYY)

25 1 Adjusting Entry

Y = Adjusting journal.

N = Regular journal (default).

26 3 Adjusting Period

Defaults to 998 for adjusting journal.

29 8 ADB Average Daily Balance Date(MMDDYYYY)

Defaults to journal date if this field isblank.




37 10 Ledger Group

47 1 Reversal Code

B = Begin next period.

E = End next period.

X = Next day.

D = User defined date.

U = Adjustment period.

N = No reversal (default).

48 8 Reversal Date (MMDDYYYY)

Populated by journal edit program if Bor E. Must have a valid date if ReversalCode is D.

56 3 Reversal Adjusting Period

Only used when Reversal Code is U

59 1 ADB Reversal Code

D = User defined date.

S = Same as journal reversal (default).

60 8 ADB Reversal Date (MMDDYYYY)Must have a valid date if ADB ReversalCode is D.

68 3 Journal Source

71 8 Transaction Reference Number

79 30 Description

109 3 Default Currency Code

Foreign currency Code. Defaults tobase currency of the business unit.

112 5 Default Currency Rate Type

117 8 Currency Effective Date(MMDDYYYY)

Defaults to Journal Date.

125 17 Default Currency Exchange Rate




142 3 System Source

EXT = Journal Edit creates VAT linesand calculates it if VAT lines are notimported (default).

EXV = Journal Edit won’t create orcalculate imported VAT lines.

145 8 Document Type for DocumentSequencing

If blank, gets value from default onrun request panel, journal source, andledger group.

153 12 Document Sequence number

Filled by document sequencing routineif document sequencing is enabled;otherwise the field is blank. Enterednumber is checked by documentsequencing.

165 1 Budget Header Status

V = Budget validated.

N = Not validated (default).

166 1 Commitment Control Amount Type

1 = Actuals (default).

2 = Encumbrance.

3 = Pre-encumbrance.

167 4 GL Adjustment Type

171 10 Journal Class

File Format for Journal Line

Flate file’s journal line format. Journal line data follows immediately after it’s header data in the file.


1 1 L

2 5 Business Unit

Defaults to Business Unit from header.If a different business unit is entered,this is an interunit line.

7 9 Journal Line Number

Defaultsto one more than the previousline number. First line defaults to 1.




16 10 Ledger

If Ledger Group is a commitmentcontrol ledger group, this is ignoredfrom the flat file and assignedaccording to commitment controlamount type.

26 10 Account

36 10 Alternate Account

46 10 Department

56 8 Operating Unit

64 6 Product

70 5 Fund Code

75 5 Class Field

80 5 Program Code

85 8 Budget Reference

93 5 Affiliate

98 10 Fund Affiliate

108 10 Operating Unit Affiliate

118 10 ChartField 1

128 10 ChartField 2

138 10 ChartField 3

148 15 Project

163 4 Book Code

167 8 Budget Period

175 10 Scenario

185 3 Statistics Code

188 28 Base Currency Amount

Calculated from transaction amount andexchange rate. If entered and exchangerate = 0, andrecalc exchange rateisselected for the journal edit request, theexchange rate is calculated.




216 1 Movement Flag

This is only used in a separate debit /credit database.

N = Natural (default).

R = Reverse.

217 17 Statistics Amount

Only valid for statistical accounts or forlines with statistic codes.

234 10 Journal Line Reference

244 30 Journal Line Description

274 3 Currency Code

Defaults to default currency on header.The journal edit program blanks this outfor a statistical account.

277 5 Currency Rate Type

282 28 Amount

Foreign Currency Amount

310 17 Currency Exchange Rate

Defaults to 1 if Currency Code = BaseCurrency. Uses table lookup in journaledit program if currency rate type isentered andrecalc exchange rateisselected for journal edit request.

327 5 Projects Business Unit

332 15 Projects Activity ID

347 3 Projects Analysis Type

350 5 Projects Resource Type

355 5 Projects Resource Category

360 5 Projects Resource Sub-category

365 8 Budget Date (MMDDYYYY)

Defaults to Journal Date if blank.

373 1 Budget Line Status

Defaults to N if blank or Budget HeaderStatus = N.

374 10 Entry Event

384 4 Inter/intraunit transaction groupnumber




388 1 Inter/intraunit anchor flag

389 30 Open Item Key

File Format for Journal VAT Line

Flat file’s journal VAT line format. Journal VAT data follows immediately after it’s journal line data in the file.


1 1 V

2 1 Physical Nature

G = Goods (default)

S = Service

3 6 Defaulting State

9 1 VAT Exception Type

N = None

S = Suspended

X = Exonerated

10 20 VAT Exception Certificate ID

30 1 Record VAT Input

Whether a business unit pays VAT andrecovers it later from VAT tax authority.Typically for purchase transactions.

Y = Yes.

N = No.

31 1 Record VAT Output

Whether VAT is collected by vendor onbehalf of the government. Typically forsales transactions.

Y = Yes.

N = No.

32 1 Calculation Type

E = Exclusive: VAT stated separatelyfrom merchandise.

I = Inclusive: VAT included withmerchandise.




33 1 Calculation at Gross or Net

G = Gross.

N = Net.

34 3 VAT Reporting Country

Required field

37 8 VAT Declaration Date

Defaults to journal date if blank.

45 4 VAT Transaction Type

Required field

49 1 VAT Applicability

Required field

E = Exempt.

N = Not applicable.

O = Outside of scope of VAT.

S = Suspended.

T = Taxable.

V = VAT only.

X = Exonerated.

50 8 VAT Code

Required field

58 4 VAT Account Type

62 1 VAT Distribution Status

D = Distributed.

E = Error flag.

I = Ignored.

M = Archival entry.

N = Not distributed.

P = Processed.

R = Reversal entry.

U = Undefined.




63 28 VAT Amount

if system source = EXV

Entered VAT amount = VAT amount;

otherwise,

entered VAT amount = 0.

91 28 VAT Amount in Base Currency

if system source =EXV

Entered VAT Base Amt = VAT BaseAmount;

otherwise,

entered VAT base amount = 0.

119 28 VAT Basis Amount

147 28 VAT Basis Amount in Base Currency

175 9 Tax Code Aggregate Percent

184 1 Override VAT Tolerance Check

Y = Override: no check.

N = Check.

185 6 VAT Use Type

191 7 Recovery percent

198 7 Rebate percent

205 28 Recovery Amount

233 28 Recovery Amount in Base Currency

261 28 Rebate Amount

289 28 Rebate Amount in Base Currency

317 1 Recovery Percent Source

A = Automatically calculated.

M = Manual entry.

318 1 Rebate Percent Source

A = Automatically calculated.

M = Manual entry.




319 1 VAT Rounding Rule

D = Round down.

N = Natural round.

U = Round up.

320 1 Amounts for Reporting Currency

Y = Yes.

N = No.

321 3 Reporting Currency

324 28 VAT Amount in Reporting Currency

352 28 VAT Transaction Amount Reporting

380 17 Currency Exchange Rate

Defaults to 1 if Currency Code = BaseCurrency.

397 1 Prorate Non-recoverable VAT

Y = Yes.

N = No.

398 1 Allocate non-recoverable VAT

Y = Yes.

N = No.

399 1 VAT Apportionment Control

D = Distribution GL business unit.

G = Transaction GL business unit.

T = Transaction business unit.

400 9 VAT Applicable Journal Line Number

File Format for Journal Control Total

Flat file’s journal control total data format. Control total data follows it’s header databut comes after journal line and journal VAT.


1 1 C

2 5 Control Business Unit

The business unit that the control totalsare for. Defaults to the header businessunit if this is blank.




7 10 Ledger

17 3 Base Currency Code

The base currency that the controltotals are for. Should always equal thebusiness unit’s base currency except forstatistical account totals.

20 3 Currency Code

The foreign currency that the controltotals are for. Defaults to the headerbusiness unit if this is blank.

23 28 Journal Control Base Currency Debits

51 28 Journal Control Base Currency Credits

79 28 Journal Control Foreign CurrencyDebits

107 28 Journal Control Foreign CurrencyCredits

135 17 Journal Control Statistical Units

152 9 Journal Control Lines

161 10 Department

171 8 Operating Unit

179 6 Product

185 5 Fund Code

190 5 Class Field

195 5 Program Code

200 8 Budget Reference

208 5 Affiliate

213 10 Fund Affiliate

223 10 Operating Unit Affiliate

233 10 ChartField 1

243 10 ChartField 2

253 10 ChartField 3

263 15 Project

278 4 Book Code

282 4 GL Adjustment Type

286 8 Budget Period




294 10 Scenario

304 2 Balance Sheet Indicator

Note. The file layout object GL_JRNL_IMPORT for flat file journal import is delivered in fixed columnformat as shown above. You can change this to CSV format and also adjust the date format if necessary.

Page Used to Import Journals from Flat Files


Flat File Journal ImportRequest

LOAD_JRNL_PNL General Ledger, Journals,Import Journals, ExternalFlat Files

Use the Load JournalsFrom a Flat File process(GL_JRNL_IMP) to loaddata from a flat file into thePeopleSoft General Ledgerjournal tables.

Importing Journals From Flat FilesAccess the Flat File Journal Import Request page.

Flat File Journal Import Request page

Character Set Select the Character Set appropriate to the flat file being processed. When theuser creates a request, the Character Set defaults to the character set associatedwith the default language code of the user that is creating the run controlrequest. You can change this value but you must have a UNICODE databaseif the Character Set of the file being processed requires UNICODE.

UNICODE is important when your database must functions in otherthan the Latin alphabet, such as Japanese Kanji.

Validate ChartFields Choose the level of ChartField validation for the import process. A lowervalidation level allows import process to run faster and make use of journalsuspense processing when Journal Edit re-validates the journal at a later stage.



Default GL Document Type If you use document sequencing, specify a default document type toindicate the business purpose for the transaction. You can specify adocument type for each journal header in the flat file.

Journal ID Mask You can enter a unique mask or prefix to readily identify journals createdthrough flat file journal import, if the journal ID is blank or NEXT in the file.

See Also



PeopleSoft Global Options and Reports 8.8 PeopleBook, “Defining Document Sequencing”

Using the Spreadsheet Journal Entry Import ProcessPeopleSoft General Ledger has a Spreadsheet Journal Import user interface. You use it to prepare and enterjournals offline without database connection. And then import them into your PeopleSoft database directly overthe internet or import them via files. Please see the following PeopleBook for full details on using this utility.

See Chapter 9, “Using Spreadsheet Journal Import,” page 173.




CHAPTER 9

Using Spreadsheet Journal Import

This chapter discusses how to:

• Set up and import spreadsheet journals.

• Make accounting entries using Spreadsheet Journal Import.

Understanding Spreadsheet Journal ImportThis section describes the prerequisites for importing spreadsheet journals into PeopleSoft GeneralLedger and presents an overview of the spreadsheet journal import process.

PrerequisitesThis table lists the three files PeopleSoft provides for the spreadsheet journal import user interface.You must copy all three files to the same folder on your workstation.

JRNL1.XLS Journal workbook that you work on to create and import journals.You can rename this file, if you wish.

JRNLMCRO.XLA Visual Basic code library and dialog control.

GLLOG.XLT Message Log template.

In addition to these three files, Spreadsheet Journal online import mode relies on a MicroSoftdelivered XML library file MSXML.DLL being on your workstation.

You work on the JRNL1.XLS workbook (or a copy of it) to create and import journals. Youmust set up your Microsoft Excel to accept macros. You can do this from your Excel Toolsmenu > Macro > Security > select Medium or Low security level.

To import journals in online mode from the spreadsheet, your system administrator mustgrant you permission to the following web libraries:

• WEBLIB_XMLLINK

• WEBLIB_GL

To import journals in batch mode, your system administrator must set up the correctenvironmental variable on the process scheduler server.

See Chapter 6, “ Integrating and Transferring Information Among Applications ,”Importing Journal Entries, page 76.


Using Spreadsheet Journal Import Chapter 9

Spreadsheet Journal Import OverviewThe Spreadsheet Journal workbook lets you enter journals offline using Excel and then import thejournals into your PeopleSoft database. It supports regular journals and standard budget journals.However, it does not support commitment control budget journals.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Entering and PostingCommitment Control Budget Journals,” Importing Budget Journals From a Flat File.

Spreadsheet Journal Import does not support user entered Value Added Tax (VAT) information.After you import the journals from the spreadsheet, the Journal Edit process creates VAT defaultsand amounts based on the country code, if VAT Is enabled.

Spreadsheet Journal Import partially supports multibook journals. You can specify a primary or secondaryledger on the multibook journal lines, but you cannot enter multiple ledger information (multibook) forthe same line. When you run the Journal Edit process, it creates the additional multibook lines.

Spreadsheet Journal Import does not allow the use of control accounts. By definition, controlaccounts originate in the subsystems, such as accounts receivable and accounts payable. SpreadsheetJournal Import will reject control accounts during the import process.

Note. After importing a journal from a spreadsheet, you must run the Journal Edit process on thejournal before you make corrections using the Create Journal Entries pages.

PeopleSoft Journal Workbook: JRNL1.XLS

The JRNL1.XLS workbook is the PeopleSoft Spreadsheet Journal Import user interface. You use it toprepare and enter journals, group and manage journals into journal sheets, and import them into yourPeopleSoft database using various pages, dialog boxes and buttons. There is a built-in utility you useto configure ChartFields and rearrange columns in your journal workbook. The workbook containsone or more journal sheets, and each journal sheet can contain one or more journals.

When you open the file JRNL1.XLS, you begin with the Control page. The Control pagecontains three sets of buttons that enable you to:

• Set workbook defaults, configure ChartFields, and rearrange columns.

• Maintain the journal sheets in the workbook.

• Import the journal sheets from the workbook.

You use the journal sheet page to prepare journals. There are buttons and dialog boxes for you to add, delete, andcopy journals. Because you are entering data offline into the spreadsheet, there is no validation of the values youare entering. Validation of journals takes place when you import the journal and during the Journal Edit process.

Online Versus Batch Mode Import

You can import data into your PeopleSoft database using Spreadsheet Journal Importin either online mode or batch mode.

• Using online mode, you open a journal sheet, enter data, and use the Import Journals Nowbutton to import the data into your PeopleSoft database. Data is sent as XML documents overthe Internet and immediately imported into the PeopleSoft database.


Chapter 9 Using Spreadsheet Journal Import

• Using batch mode, you can store your journal sheets by using the Write Journals to aFile button, and then run the Batch Import Process (GL_EXCL_JRNL) to import one ormore journal files into your PeopleSoft database.

Batch import mode has a feature to import multiple journal files at a time using an index file that points tomultiple data files. For example, assume you have a text file INDEX.TXT containing these four lines:

H:\helen\JRNL1.xml

H:\helen\JRNL2.xml

H:\david\JRNL1.xml

H:\Singapore\ProjectX.xml

You can attach INDEX.TXT to the Spreadsheet Journal Import page and selectIndex file to other data filesin the Number of Data Files field. The Spreadsheet Journal Import process searches for all four data filesand imports them one by one. Be aware that the file paths are specified relative to the process schedulerwhere the import process runs. In this example, it is theH drive on the process scheduler.

If your process scheduler runs on a Unix machine, then your index file may look like thefollowing example. Remember,Unix file names are case sensitive.

/tmp/usr/jrnl1.xml

/tmp/usr/jrnl2.xml

/tmp/usr/jrnl1.xml

/tmp/singapore/projectx.xml

Setting Up and Importing Spreadsheet JournalsThis section discusses how to:

• Use the Spreadsheet Import Control page.

• Set up workbook defaults.

• Creating a new journal worksheet.

• Enter journals using journal sheets.

• Import journal sheets in online mode.

• Import journal sheets in batch mode.



Pages Used to Set Up and Import Spreadsheet Journals


Spreadsheet Journal Import -Control Page

JRNL1.XLS Click on JRNL1.XLSfile delivered with yourPeopleSoft products to openthe Spreadsheet Journal -Control Page.

Use to set the defaults andset up your spreadsheetsfor importing into GeneralLedger.

Define Options and DefaultsJRNL1.XLS Click the Setup button on theSpreadsheet Journal Import- Control page.

Set journal header defaultsand options for messagelogging, documentsequencing and generaloptions, and specify onlineimport controls for theworkbook.

ChartField Configuration JRNL1.XLS Click the Configure button. Accesses a ChartFieldConfiguration secondarypage for a journal sheetwhere you can configure thecolumns and field formatsfor different ChartFields.

Notes JRNL1.XLS Click the Notes button onthe Control page.

Accesses a Notes sheet inthe workbook to use forinstructions, calculations,notes, and so on. In ourexample, the sheet is blankexcept for a heading and thecontrol button that returnsyou to the control page.

Journal Sheet JRNL1.XLS Click the New or Edit buttonon the Control Page to createor edit a journal sheet.

Use to create and editjournal data.

Spreadsheet Journal BatchImport Request

GL_EXCL_JRNL General Ledger, Journals,Import Journals, SpreadsheetJournals

Use to run batch import ofjournal sheet files thatyou created from theSpreadsheet interface intoyour PeopleSoft database.

Using the Spreadsheet Journal Import Control PageAccess the control page by opening JRNL1.XLS. If Excel asks, choose to Enable Macros.



The Control Page—Spreadsheet Journal Import

Control Page: General

The General group box enables you to define options and defaults for this workbook and toenter any notes or calculations concerning this import.

Setup Click to set up the button to access the Define Options and Defaultsdialog box. Use to set journal header defaults, message logging options,document sequencing options, online import controls, and so on. You canalso access the ChartField configuration dialog from here.

Notes Click to access a scratchpad in the workbook. Use this for instructions,calculations, notes, and so on. In our example, the sheet is blank except for aheading and the control button that returns you to the control page.

Control Page: Journal Sheets

The Journal Sheets group box enables you to insert a new journal sheet, or edit,delete, or copy an existing journal sheet.

New Click to insert a new journal sheet. A workbook can containas many journal sheets as needed, and each journal sheet cancontain as many journals as desired.

Edit Click to edit one journal sheet in the workbook.

Delete Click to delete one or more journal sheets in the workbook.

Copy Click to copy one journal sheet to a new journal sheet saved under a new name.



Control Page: Import Journals

The Import Journals group box enables you to import one or more of the journalsheets and save journal sheets to a file.

Import Now Click to initiate online import of one or more journal sheets. The systemonly imports journals that are marked asimport.

Write File Click to save selected journal sheets to a file. After saving one ormore files, you must run the batch import process (GL_EXCL_JRNL)to complete the file import process.

Note. You can use Shift + mouse click and Control + mouse click to select multiple journal sheets.

Setting Up Workbook DefaultsBefore you start entering journals, you must specify the options, defaults and settings for thejournal sheets in your workbook. From the Spreadsheet Journal Import control page, click theSetup button to display the Define Options and Defaults dialog box.

Define Options and Defaults: Header Defaults

Enter defaults for Business Unit, Date, Ledger Group, Source and the following fields as necessary.

Spreadsheet Journal Import - Journal Header page

User ID Enter the default (operator) user ID for the journal header.

Enable Multibook Select this field to make the Ledger field in the New Journal Header pageunavailable for selection. This ledger field displays when you click the Addbutton in the Spreadsheet Journal Import — Header section of the worksheet.



The Ledger field on the journal header is optional. You only use it when youwant to enter journals for ledger groups that arenot set toKeep Ledgers inSyncand for which you do want to specify the ledger name on the header.

If you select this check box, the Ledger field is not enabled on the journal header.

AutoGen Lines(automatically generate lines)

This field is related to the Keep Ledgers in Sync (KLS) option for multibookledgers on the Detail Ledger Group page. The KLS option determines if atransaction is posted to one or to all ledgers in a group.

If you select this option, the system automatically generates journallines to support transaction detail for all ledgers in a ledger group. Forexample, if you enter a two-line journal import for a ledger group thatcontains three ledgers, the journal edit process generates an additionalfour lines—two lines for each additional ledger.

If you do not select AutoGen, and the Ledger Group of the journal is definedas KLS, then the Journal Edit process overrides your choice and generatesthe corresponding lines anyway for all ledgers in the group.

Define Options and Defaults: Message Options

Define the message log options based on the following information:

Message Options Log Error Messages Only:The system logs import messages toJRNLLOG.XLS only when errors occur.

Log Successful and Error Messages:The system logs all import messages toJRNLLOG.XLS regardless of the import process being successful.

Display Messages Online Select to show import error messages online. Otherwise, errors goonly to the message log JRNLLOG.XLS.

Define Options and Defaults: Document Sequencing

Define document sequencing options based on the following information:

Enable DocumentSequencing

Select to enable document sequencing for any business units that use it. Youcan track journals by document sequence number. Enabling this option allowsyou to specify Document Sequencing fields on the journal header.

Default Document Type When document sequencing is enabled, specify a default document type—suchas domestic customer invoices, customer credit memos, or customer debitmemos—to indicate the business purpose of your transaction. You canenter a document type for each journal header at a later time.

Define Options and Defaults: Online Import Control

Define options and behavior of online import mode based on the following information:

Address Enter the URL of the PeopleSoft XMLlink web service. To use a secureconnection, contact your Information Technology department to set upa secure socket layer (URL starts with https://).



User ID(identification) Database PeopleSoft logon User ID.

After Successful Import Change Import Status to Do Not Import:The system changes import statusof journals that are imported successfully. This prevents reimport of thejournals when you attempt to import them a second time.

Keep Import Status as Import:Select this if you do not want the systemto change import status so that you can re-import it later.

You can override journal import status at the journal sheet level anytime.

Note. To verify that your URL address is correct, copy the address to a browser and press enter.You should be able to see a list of PeopleSoft xmllink services.

Chartfield Configuration in Spreadsheet Journal Import

Click the Configurate button on the Define Options and Defaults page to access the ChartFieldConfiguration dialog, in which you can include, exclude or rearrange columns, as well asalter field labels and column formats for a worksheet.

Spreadsheet Journal Sheet - ChartField Configuration

You can alter the contents of your spreadsheet one column at a time. The column that youintend to edit is highlighted in blue. The Chartfield configuration - Column page enablesyou to select a column and control its appearance.

ChartField Configuration – Column

Use this dialog to change the format, ChartFields, and column layout of your spreadsheet.



Select the buttons on the ChartField Configuration dialog based on the following information:

Moves the highlight one column to the left.

Moves the highlight one column to the right.

Shifts the highlighted column to the left.

Shifts the highlighted column to the right.

Inserts a new column to the left of the highlighted column.

Click this button to increase the width of the highlighted column.

Click this button to reduce the width of the highlighted column.

Note. The configuration dialog prevents you from deleting or modifying certain system required fields.

ChartField Configuration – Field Format

Use the ChartField Configuration - Field Format dialog to control the content andformat of the columns on your spreadsheet.

ChartField Configuration− Field Format page

Field Name You must use a valid database field name from PeopleSoft journal tables. Ifyou misspell a field name or enter an invalid field name, you will not receivean error message until you attempt to import the journal sheet.

Label Enter the column label for the spreadsheet journal workbook.

Format Specify the cell format.



Apply You mustclick to save this format for the journal sheet.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Configuring ChartFields”

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Defining DocumentSequencing,” Defining Document Types

Creating a New Journal WorksheetClick the New button on the Spreadsheet Journal Import control page to access the New Journal Header page.

New Journal Header page

Unit, Journal ID, JournalDate, Ledger Group,Source,andUser ID

Enter the GL business unit and these other required fields . Fieldsthat your organization chose not to implement are unavailable. Forexample, if you chose not to implement document sequencing, thosefields are unavailable. A field may also be unavailable depending onthe settings on the Define Options and Defaults page.

AutoGen Lines(automatically generate lines)

Select this check box if the ledger group contains multiple ledgers. If you haveselected the Keep Ledgers in Sync (KLS) option for multibook ledgers on theDetail Ledger Group - Definition page, you should always select the AutoGenerate Lines check box so that the system automatically generates journal



lines to support transaction detail for each ledger in the group. For example, ifyou enter a two-line Journal import for a Ledger Group that contains threeledgers, the journal edit process will generate two lines for each ledger.

Entering Journals Using Journal SheetsAccess a new journal sheet.

New Spreadsheet Journal Sheet

Imports this journal sheet immediately using online import mode.

Returns to the Spreadsheet Journal Import control page.

Spreadsheet Journal Import - Header Buttons

The buttons in the Header section of the spreadsheet are:

Creates a new journal header with its own default values.

Selects the journal header on whose lines you want to work.

Edits the journal header fields.

Copies a journal.

Deletes a journal.

Changes import status of a journal.

Spreadsheet Journal Import - Lines Buttons

The buttons in the Lines section of the spreadsheet are:



(in the Lines section)Adds a journal line in the current selected journal header.

(in the Line section)Deletes a journal line. Position your cursor on the line and click this button.

Copies a block of multiple lines.

Deletes a block of multiple lines.

Adding Journal Lines

Click Add button to access add a journal line.

Inserting a Journal Line

1. Populate the journal line data using the TAB key or arrow keys to advance from one cell to another.

2. Insert additional lines by clicking the Add sign again to insert a line and automatically repositionyour cursor in the first active cell of the new line. Scrolling left is unnecessary.

3. Select the check box for a field where you want the value of the field on that journal line repeated in thejournal line that is added next. Otherwise, the value for that field on the succeeding line is blank.

Note. Use as many journals in a spreadsheet as you like. Note that when you insert lines,they carry the header displayed at the top of the sheet.

Importing Journal Sheets in Online ModeYou can import journal sheets online from either the control page or the journal sheet page.

Import Journals Online From the Spreadsheet Journal Control Page

Access the Import Journals Now dialog by clicking Import Now on the Spreadsheet Journal Import control page.



Import Journals Now page

Select the sheets you want to import into PeopleSoft General Ledger database. Enter yourPeopleSoft database User ID and Password and click OK.

Import Journals Online From a Spreadsheet Journal Worksheet

Access a Spreadsheet Journal Import journal sheet.

Click this button to display the Import Journals Now page.

Import Journals Now page

The URL to your PeopleSoft database appears automatically. Enter your User ID andPassword and click OK to import the journals.

Importing Journal Sheets in Batch ModeSome organizations create numerous journal sheets, which they store in flat files for processingat a later time. To do this, you must write the journal sheets to the individual flat files. Whenyou are ready, you run the GL_EXCL_JRNL batch import process.

Writing Journals to a File

After completing your journal sheet activity, navigate to the Control page and click WriteFile to access the Write Journals to File dialog.



Write Journals to File page

Select some or all journal sheets that you want to save and click OK. This stores the Journal Sheet datain the file you specify in File Name. To import the journal file into the PeopleSoft database, you mustrun the PeopleSoft Spreadsheet Journal batch import process (GL_EXCL_JRNL).

Running the Spreadsheet Journal Import Batch Process (GL_EXCL_JRNL)

Access the Spreadsheet Journal Import Request page in PeopleSoft General Ledger.

Spreadsheet Journal Import Request page

Number of Data Files Single data file:The file you attached to this page is the datafile containing journal data.

Index file to other data files:The file you attached to this page is an index filecontaining file path and file names to one or more data files stored elsewhere.

Add Click to add an attachment. Browse for the file you have written fromthe spreadsheet journal workbook, and then click Upload.

Delete Click to delete an attachment.

View Click to display the contents of the attached file.



Character Set Select the character set of the flat file being imported. For example, you canspecify ISO_8859-6 for Arabic or JIS_X_0208 for Japanese Kanji.

If Journal Already Exists SelectAbort , Skip,or Update

If Journal is Invalid SelectAbort or Skip.

Default GL Document Type If you use document sequencing, specify a default document typeto indicate the business purpose for the transaction. You can enter adocument type for each journal header at a later time.




CHAPTER 10

Processing Journals

This chapter provides an overview of processing journal entries and discusses how to:

• Determine the status of journals

• Request Journal edits

• Post journals

• Unpost journals

• Handle journal errors

• Work with suspense and journal corrections

• Produce journal reports

Understanding Journal ProcessingPeopleSoft General Ledger offers several ways to process journals to ensure control and maximize efficiencywithout losing flexibility. You decide when and by whom journals are validated and posted. Allow oneuser to only enter the journal entries, and allow another user to post these journal entries.

Common TerminologyWhen you select and inquiry or process, you often have the opportunity to specifically identify characteristicsof the data that you want to use to inquire upon or process. This selection criteria might include:

Process Frequency The options in the box control how often a request is processed. If youselect Once, the system will process the current request the next time abackground Edit is executed for the Run Control ID. Once executed, theProcess Frequency status is changed to Don’t Run. If you want this request tobe processed each time editing is initiated, select Always.

Request Number The field indicates the number for the process request. The system assignseach set of run parameters a unique number. The process edits journalsin the ascending order of the request number.

Business Unit Specify value to edit journals for that business unit only or leave it blank toedit journals for all business units. If you specify a business unit value,Journal Edit will also edit the non-anchor business unit journals for whichthe anchor business unit is the specified business unit.


Processing Journals Chapter 10

Ledger Group Select to edit journals for a specific ledger group, or leave blankto edit journals for all ledger groups.

Source Select to edit journals for a specific journal source, or leave it blankto edit journals for all journal sources.

System Source You can specify a system source to limit journal selection to specific generalledger processes or specific application processes. For example, you couldinclude only journals that the Allocations process or theJGen-AR(JournalGenerator process for PeopleSoft Receivables transactions) created.

Process Partition ID Specify a process partition ID to limit journal selection to specific data setsthat you define for the partition ID on the Process Partition page. Each data setis associated with a business unit and ChartField combination.

Journal ID From/To, Enter a range of journal ID numbers to limit the number of journals to process.

Journal Date From/To Enter a journal date range to limit the number of specific journalswithin a given period to process.

From Year/Per (fromyear/period) and ToYear/Per (to year/period)

Select to limit to journals within a specific range of fiscal years and periods.

Journal ProcessingBefore you can post journals to PeopleSoft General Ledger you must edit them to verify that:

• ChartField values are valid.

• Debits equal credits.

• Journal entries are flagged for posting to the target ledger.

• Inter/IntraUnit balancing entries are generated.

If the Journal Edit (GL_JEDIT) process encounters any errors, PeopleSoft General Ledger respondsbased on whether you indicated that you want to recycle the journals with errors, correct the errors, andthen post them, or whether you indicated that you want to post the journals with invalid ChartFieldsor unbalanced debit and credit amounts to your suspense accounts.

There are two methods to edit and post journals:

• Select the Journal Edit and Journal Post options from the menu.

• SelectEdit JournalandPost Journalduring journal entry.

When you edit or post while making journal entries, the system initiates the processes on the server. When theprocess is complete, the system automatically updates the Journal Entry pages with the results of the edit or post.

To streamline the Journal Edit (GL_JEDIT) and Journal Post (GLPPPOST) processes, you cancombine and run the processes by selecting both Edit and Post on the Journal Edit - Request page.The system posts all journals without errors that pass the Journal Edit process.


Chapter 10 Processing Journals

The Journal Post process:

• Posts on valid, edited journals.

• Posts each journal line in the appropriate target detail ledger.

• Changes the journal’s status to posted.

Note. PeopleSoft General Ledger doesnot post unbalanced journals to balanced ledgers.

After posting, the system retains the original journal entries for analysis and an audit trail. You can reverseposted journal entries with a full audit trail, and you can alsounposta journal. Unposting is aone timeonly event for any one journal, and there are restrictions—you cannot edit the journals.

The Review Journal Status component provides a summarized display of journal entries. Once allcritical entries are processed, you can schedule closing and reporting tasks.

See Also



PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Defining Common Journal Definitions

Journal EditingThe Edit Journals Request page enables you to specify selectively which journals to edit, based on thebusiness unit, ledger group, journal source, system source, process partition ID, journal ID, and journal date.PeopleSoft General Ledger will edit only those journals that match your request criteria. If you leave onecriterion blank, PeopleSoft General Ledger ignores that criterion and edits journals that match the othercriteria. For example, you can run edit for all business units by leaving the business unit field blank.

Note. To initiate a journal edit without going to the Edit Journals Request page, use the EditJournal option in the Process field on the journal Lines page.

You can combine the Journal Edit (GL_JEDIT) and Budget Checking (FSPKBDP2) processes in a single runby selecting both Edit and Budget Check on the Edit Journals Request page. The system budget checks thejournals that pass edit. You can also combine the Journal Edit (GL_JEDIT), Budget Checking (FSPKBDP2),and Journal Post (GLPPPST2) processes in a single run by selecting Edit, Budget Check, and Post on theEdit Journals Request page. The system will post the journals that pass editing and budget checking. Ifyou do not use the commitment control option, you can ignore the Budget Checking option.

When you run the process, you can run the Journal Edit process exclusively or you can run a Journal Edit andError Rpt (report) multiprocess job (GLJEDERR) that runs the Journal Edit process and generates an error report.



Journal PostingYou can request posting at the time you enter journal entries or at a later time.

Most journal entries generated by a company will be posted in a background process that typically occurson a daily or weekly basis. In this case, you mark journals for posting so that all pending journals areprocessed together the next time you run the Journal Post (GLPPPOST) process.

When you mark a journal for posting, PeopleSoft General Ledger verifies that no outstandingedit errors exist in the journal that renders it invalid for posting.

There are times, however, when an immediate request to post is warranted. Posting from the journalentry Lines page provides you with that flexibility. To initiate a journal post without going to the PostJournals Request page, selectPost Journalin the Process field on the journal Lines page.

For special types of requests, such as posting groups of journals, use the Journal Post(GLPPPOST) process. Posting performs the following:

• Selects all journals that have been marked for posting and that meet the criteria specified on the posting request.

• Posts the lines of each selected journal to the ledger.

• Creates a reversal journal if so requested on the journal header.

• Changes the Status indicator for each of the journal fromValid to Posted.

• Changes the status of the sibling rows in the Open Item table toOpenand subjects the rowsto reconciliation if the journals contain Open Item accounts.

PeopleSoft General Ledger then posts the individual journal lines to the target ledger. Journal Post alsoperforms one or more of the following jobs if you select the options when you run the process:

• Reconciles Open Items for transactions related to currently posted journals.

• Updates Average Daily Balance information.

• Updates Summary Ledgers incrementally.

• Updates ledger balances incrementally for ledgers that are loaded from external sources.

The process populates the Posting Date on the journal header using the Journal Process Date thatyou define for each business unit on the General Ledger Definition − Journal Options page for thePost Date for all journals in the batch. It can be the date at the time the Journal Post process beginsor a date of your choosing. If you prefer to maintain a user-specified date for posting date, you canautomatically update the date for a single business unit, a range of business units, or all business unitsby running the Maintain GL BU Process Date process (GLPROCESSDT).

You can also run the Post Daily Balances process (GL_ADB_POST) after you post journals from the PostJournals Request page. The Journal Post process posts daily balances to an intermediate holding table. TheADB Post process posts daily balances from the intermediate holding table to the ADB ledger (also known asthe daily ledger or ADB source ledger). After it posts the daily balances to the ADB ledger, it deletes therows in the holding table. Or you can run the Journal and ADB Post (journal and average daily balance post)multiprocess job (GLADBPST) to post the journals and update the ADB ledger with the daily balances.

Note. Journals cannot be posted or unposted to a closed period. The closed period must firstbe opened before any journal activity can be processed in that period. The Transaction Typeto look for on the Open Period Update page is ’UNP’.



See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,”Defining Default Journal Post Options for a Ledger

Chapter 14, “Calculating Average Balances,” page 255

Chapter 10, “Processing Journals,” Setting the Process Date, page 205

Unposting JournalsYou can unpost a journal only once, and you cannot edit a journal that you have unposted. If you wantto post a journal that has been unposted, just copy the journal to a new journal and post the new journal.PeopleSoft General Ledger automatically creates an unpost audit trail for you.

When you unpost a journal with related journal entries, the process automatically unposts the related journalentries too. For example, when you unpost an accrual journal entry, the accrual reversal journal entry isautomatically unposted at the same time. The same is true for unposting interunit journals and suspense journals.

The original journal entry is the anchor journal entry and the journal entries that the system generates foraccrued reversals, interunit entries, and for suspense journal lines are non-anchor journal entries.

The Journal Post process (GLPPPOST) searches for anchor journals that are to be unposted. Itidentifies non-anchor journal entries by looking for the following:

Reversal journals Journals whose reversal code is one of the following:

Beginning Of Next Period

On Date Specified By User

End Of Next Period

Next Day

Adjustment Period

InterUnit journals Journals whose InterUnit business unit field is different fromthe business unit field.

Suspense correctionjournals

Journals that contain an entry in the PS_JRNL_HDR_SIBL table.

Reversal journals are selected and marked for unpost based on business unit, ledger group, journalsource, fiscal year and accounting period (including adjustment periods), specific journal ID (optional),ChartField criteria, journal class criteria, and journal date range (optional). Entry event lines generatedwith the journals are reversed (unposted) along with their associated journals.



Note. The capability to mark journals for unposting by ChartField criteria and journal class criteriais important to the processing of reversals performed by the federal government. The governmentrequires the capability to perform reversals on transactions involving trading partners. Since TradingPartner is set up as a ChartField by the federal government, the government can easily perform thesereversals using unposting. The federal government also sets up journal classes to categorize types ofjournals. Processing reversals by journal class using the unpost feature enables the government toprocess a large number of reversals falling within a specific category together.

The Journal Post process (GLPPPOST) then tries to unpost the related non-anchorjournals. The process does one of the following:

• If the non-anchor journals are posted, the process unposts them with the anchor journals.

• If the non-anchor journals are not posted, the process creates the unpost journals to offset thenon-anchor journals, and then the process marks both the anchor and non-anchor journals for postingand posts them. This creates an audit trail for the non-anchor journals.

Note. Journals cannot be posted or unposted to a closed period. The closed period must firstbe opened before any journal activity can be processed in that period. The Transaction Typeto look for on the Open Period Update page is ’UNP’.

The Automatically Unpost options are selected by the system for both non-anchor interunit andnon-anchor reversal journals. The system always unposts non-anchor journals entries with the anchorjournal entry. You can query and display the non-anchor journals on the Mark Journal for Unpostingpage, but they are unposted only when you unpost the anchor journals.

PeopleSoft General Ledger can unpost journals that contain Control Accounts in General Ledger; however,it does not automatically keep the feeder system for which the control account exists in sync. This must bedone in the feeder application or in the feeder system (Payables, Receivables. Treasury, and others).

Note. Deleting a journal entry that has never been posted is a distinct process from unpostinga journal entry that has been posted. Deleting an unposted journal entry is describe in thechapter Making General Ledger Journal Entries.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Deleting Journal Entries Not Yet Posted, page 159

Changing the Unpost Journal Date for Business UnitsWhen you want the flexibility to change the unpost date for a journal entry, access the businessunit’s Journal Options page and check Allow Different Unpost Date box. This makes the UnpostDate field available on the Mark Journals for Unposting page.

The date you enter in the Unpost Date field becomes the journal dateon which the original journal isunposted. Unposting creates a new journal entry to reverse the old. This new journal entry has the UnpostDate as its journal date or retains the journal date of the original journal that is being reversed.



Note. For InterUnit journals, all business units must have the Allow Different Unpost Date option selectedon the General Ledger Definition - Journal Options page if you want to change the journal unpost date.If one business unit does not have this option selected, you receive an error message.

See Also

Chapter 3, “Defining Your Operational Structure,” Defining Journal ProcessingOptions for a Business Unit, page 30


Journal Error ProcessingJournal error processing options are available at the Business Unit, Ledger For A Unit, and Sourcelevels. Error processing options defined at the Ledger For A Unit level will override those definedat the Business Unit level; error-processing options defined at the Source level override optionsdefined at both the Business Unit and Ledger For A Unit levels.

Journal Error Processing Override Diagram

The Suspend journal error processing option can be set for these errors:

Journal Balance Errors A journal balance error occurs when an unbalanced journal is created witha ledger that is defined as a balanced ledger. If the Suspense option is set,the system will generate a suspense line(s) to bring the journal into balance.This suspense line is referred to asa balance suspense line.

Journal Edit Errors A journal edit error occurs if the journal line has an invalid ChartFieldvalue or ChartField combination. If the suspense option is set, a suspense



line will be generated for each line that is in error. This suspenseline is referred to as an edit suspense line.

Journal Amount Errors A journal amount error occurs if a foreign currency journal line has differentsigns on foreign amount and monetary amount. If the suspense option isset, a suspense line will be generated for each line that is in error. Thissuspense line is referred to as an amount suspense line.

At any level, you can select the ChartFields and ChartField values for your amount, balance and edit suspense.The Journal Edit process will create the suspense lines with the ChartFields and ChartField values you selected.

See Also



Journal Error and Suspense Journal TerminologyPeopleSoft General Ledger gives you the option to suspend unbalanced amounts and amounts fromlines with edit and/or amount errors. The Journal Suspense Correction process makes it easy for youto identify and correct journals that have transactions posted to suspense accounts.

When we discuss Journal Suspense Correction, we will use the following terminology:

Suspense Journal Journal that has transactions posted to suspense ChartFields.This journal contains amount suspense lines, balance suspenselines and/or edit suspense lines.

Balance Suspense Line Suspense line generated by the Journal Edit process. This line is requiredto bring an out-of-balance journal back into balance.

Edit Suspense Line Suspense line generated by the Journal Edit process that references a journalline with invalid ChartFields and/or ChartField combination errors.

Amount Suspense Line Suspense line generated by the Journal Edit process that referencesa foreign currency journal line with foreign amounts and monetaryamounts of different signs.

Corrections Journal Journal created from the Suspense Journal Correction process that correctsand reverses suspense transactions for a suspense journal.

Balance Correction Line Journal line generated by the Suspense Journal Correction process tocorrect the balance suspense line on a suspense journal.

Edit Correction Line Journal line generated by the Suspense Journal Correction process tocorrect the edit suspense line on a suspense journal.

Amount Correction Line Journal line generated by the Suspense Journal Correction process tocorrect the amount suspense line on a suspense journal.



Reversal Suspense Line Journal lines generated by the Suspense Journal Correction process toreverse the suspense lines on a suspense journal.

Suspense JournalsA suspense journal contains suspense lines generated from the Journal Edit process.

Journal processing uses a suspense status flag (SUSP_RECON_STATUS) on journal header record(JRNL_HEADER) to determine the life cycle of a suspense journal.

0 No suspense transactions—the journal has no amount, balanceor edit suspense lines.

1 Suspense transactions—the journal has balance, edit, and/or amountsuspense lines, and now becomes a suspense journal.

2 Corrections Journal Created—a corrections journal is created to correctand reverse the suspense transactions on a suspense journal.

3 Corrections Journal Posted—the corrections journal, created to correct andreverse the suspense transactions on a suspense journal, is now posted.

Warning! It is possible for a corrections journal to contain suspense lines caused by amount errors,edit errors and/or out of balance conditions. If the corrections journal has suspense lines, it becomesa suspense journal with the status of1 and the suspense cycle starts again.

Determining the Status of JournalsAt any time during journal processing, you can view the status of journals and the journalline details on the Review Journal Status pages.


• View the journal header information.

• View journal line details.

Pages Used to View the Status of Journals


Journal Header JOURNAL_HEADER_FS General Ledger, Journals,Process Journals, ReviewJournal Status, JournalHeader

Review journal headerinformation.

Journal Lines JOURNAL_LN_FS General Ledger, Journals,Process Journals, ReviewJournal Status, Journal Lines

Use to view line details forthe journal.



Viewing the Journal Header InformationAccess the Review Journal Status - Journal Header page.

Review Journal Status − Journal Header page

The top of the page displays the journal header information that you entered on the Journal Entry - Header page.

It also displays the Status for the journal, which can be one of the following:

• Deleted − Anchor Journal Unposted

• Journal Entry Incomplete

• Journal has Errors

• No Status - Needs to be Edited

• Posted to Ledger (s)

• Posting Incomplete − Repost ASAP

• Unposted

• Upgrade Journal − Can’t Unpost

• Valid journal. Edits completed

• Valid SJE Model − Do not Post

The Journal Line Totals group box displays the number of Lines in the journal entryand the total amount of the Debits and Credits.

The Commitment Control Amount Type group box displays your settings for the controlbudget if you use the commitment control option.

The Amount Type can be one of the following:

Actuals and Recognized The journal records the actual amount of a transaction, expenditure, or revenue.

Encumbrance The journal is not an actual transaction yet. Instead, it records theamount that you can legally spend. This usually occurs when youcreate a contract or a purchase order.



Pre-Encumbrance The journal is not an actual transaction yet. Instead, it records the amount thatyou will spend. This usually occurs when you create a requisition.

Collected Revenue The journal records the collected amount from a prior revenue transaction.

Actuals, Recognizedand Collect

The Journal records the actual and collected amount of a revenue transaction.

Planned The journal records the amount that you plan to spend. This amountis only an estimate; it is not an actual transaction yet.

Note. If Override is selected, the journals can exceed their budgeted amount. The UserID identifies the individual who enabled the override.

Viewing Journal Line DetailsAccess the Review Journal Status - Journal Lines page.

Review Journal Status − Journal Lines page (1 of 2)

Review Journal Status − Journal Lines page (2 of 2)

Journal Line Data This group box lists the journal line data, including your template’sChartFields, the Transaction Amount DR, Transaction Amount CR, BudgetDate, for Commitment Control transactions, is the date that is checkedagainst the Commitment Control budget ledger to ensure that it fallswithin an open Commitment Control budget period. The Rate Type andExchange Rate that the system used to convert amounts from the transactioncurrency to the base currency displays on the line.

The Budget Status is displayed for the control budget ledger if youuse the Commitment Control option and can be:

• Error

The entry failed to pass budget checking.

• Not Chk’d(not checked)

The Budget Processor has not processed the entry.



• Valid

The entry passed budget checking and the process updated the control budget.

• Warning

The Budget Processor issued a warning. This means the control budget didnot have sufficient funds. However, it passed budget checking because theCommitment Control Option for the control budget is set to Tracking withBudget or Tracking without Budget on the Control Budget Definitions page.It may also be over the budget amount, but less than the tolerance amount.

The last field that displays on the journal line is N/R, which indicates:

• N if the line amount is a normal debit or credit.

• R if the line amount is a reversed debit or credit.

Requesting Journal EditsThis section provides an overview and discusses how to:

• Run the journal edit process.

• Check the status of edit requests.

• Correct journal edit errors.

• Find journal entry errors.



Pages Used to Perform Journal Edit


Edit Journals Request JOURNAL_EDIT_REQ General Ledger, Journals,Process Journals, EditJournals, Edit JournalsRequest

Use to edit journals andoptionally to post them.

Message Log PMN_BAT_MSGLOG General Ledger, Journals,Process Journals, EditJournals, Edit JournalsRequest page. After runningthe Journal Edit process,click the Process Monitorlink to access the ProcessList page. Click the Detailslink to access the ProcessDetail page. In the Actionsgroup box, click the MessageLog link.

Displays the ProcessInstance, Name, and Typeof process, along witha list of messages, whichincludes the severity, logtime, message text, and anexplanation of the text.

Journal Entry - Lines JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries, Lines

Use to view journal entryerrors by clicking theX inthe Error column on thejournal lines page

Journal Entry - Errors JOURNAL_ENTRY_E_IC General Ledger, Journals,Journal Entry, Create JournalEntries, Errors

Use this page to determinewhich errors the systemencountered.

Review Journal Status - Findan Existing Value

SEARCH General Ledger, Journals,Process Journals, ReviewJournal Status, Find anExisting Value

Use to search for journalswith errors for a specificbusiness unit.

Running the Journal Edit ProcessAccess the Edit Journals Request page.



Edit Journals Request page

Edit Select to edit the journals.

Post Select to automatically post the journals that pass edit and budgetchecking (commitment control journals).

Re-Edit. Edited journals are flagged as either having errors or as valid (edit complete).You can edit valid journals more than once by selecting this check box. If youdon’t select this check box, the system ignores valid journals.

Recalc Exchange Rates(recalculate exchange rates)

If your journals are recorded in multiple currencies, click to recalculatebased on the most current exchange rate.

Mark Journal(s) to Post Select to mark each valid journal with a posting request status. If PeopleSoftWorkflow is activated, this option is not available.

Budget Check Select to run the Commitment Control Budget Processor (FSPKBDP2)process to check the journal against the control budget.

See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “ProcessingSource Transactions Against Control Budgets”

PeopleTools PeopleBook: “PeopleSoft Process Scheduler,” Understanding PeopleSoft Process Scheduler


Chapter 7, “Optimizing General Ledger Performance,” Using Partition IDs, page 102



Checking the Status of Edit RequestsAccess the Message Log page.

After you run a batch process, you may want to review any messages that were produced toensure the process completed without errors. Use Message Log Search and Results to checkthe status of the current request or of past processing requests.

Correcting Journal Edit ErrorsAccess the Journal Entry − Lines page.

When you encounter errors during editing, PeopleSoft General Ledger marks the journal and either recycles orsuspends it. The system saves recycled journals but does not post them until you have corrected the errors. Youcan post entries with invalid ChartFields or unbalanced debit and credit amounts to your Suspense account.You define error-processing options at the business unit, ledger for a unit, and journal source level.

To view journal entry errors, click theX in the Errors column on the Journal Entry- lines page to go to the Errors page.

Click the Line number for the line in error on the Journal Entry - Errors page to go directlyto the Journal Entry Lines page, where you can view one or all of the lines in error. Thecursor will be positioned on the line and field in error.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Viewing Journal Entry Errors, page 141

Finding Journal Entry ErrorsAccess the Review Journal Status - Find an Existing Value page.

Review Journal Status Search page



Use the Review Journal Status page to find journal entries with errors. When you enteryour search criteria on the page, selectJournal Has Errorsin the Journal Header Statusfield. This displays a list of journal entries with errors.

Note. If you track journals by Document Sequence Number, you can enter that number on this page.

See Also

Chapter 10, “Processing Journals,” Determining the Status of Journals, page 197

Posting JournalsThis section provides an overview and discusses how to:

• Set the process date.

• Mark journals for posting.

• Run the journal post process.

• Check the status of posting requests.

Pages Used to Post Journals


Maintain Process Date GL_BU_PROCESS_DT Set Up Financials/SupplyChain, Business UnitRelated, General Ledger,Maintain Process Date

Use to run the Maintain GLBU Process Date process(GL_PROCESSDT) thatupdates the Process Datefor a business unit on theGeneral Ledger Definition -Journal Options page.The Journal Post process(GLPPPOST) uses this datefor the Post Date for thejournals that it posts.

Mark Journals for Posting JOURNAL_POST_MARK General Ledger, Journals,Process Journals, MarkJournals for Posting

Use to mark one or morejournals for posting.Journals to be posted mustfirst be marked for posting.Marking a journal forposting indicates that thejournal should be includedin any posting request thatis pending for which thejournal meets the criteriaspecified. This enables youto exclude certain journalsfrom posting until youreview and approve them.



Page Name Object Name Navigation UsagePost Journals Request JOURNAL_POST_REQ General Ledger, Journals,

Process Journals, PostJournals, Post JournalsRequest

Use the Post JournalsRequest page to selectivelyspecify which journals youwill post based on theirbusiness unit, ledger group,accounting period/fiscalyear, source, journal ID, andjournal date. You can run theJournal Post process for allbusiness units. When yourun the posting process, thesystem will post only thosejournals that fit the requestcriteriaandare marked topost. (You also run the PostDaily Balances process(GL_ADB_POST) processfrom this page.)

Message Log PMN_BAT_MSGLOG General Ledger, Journals,Process Journals, PostJournals, Post JournalsRequest page. After runningthe Journal Post process,click the Process Monitorlink to access the ProcessList page. Click the Detailslink to access the ProcessDetail page. In the Actionsgroup box, click the MessageLog link.

Displays the ProcessInstance, Name, and Typeof process, along witha list of messages, whichincludes the severity, logtime, message text, and anexplanation of the text.

Setting the Process DateAccess the Maintain Process Date page.



Maintain Process Date page

The Business Unit Option group box controls for which business units the Journal Process Date is to be updated.

All Updates all business units.

Range Updates a range of business units that you specify in the BusinessUnit From and Business Unit To field.

Value Updates the specific business units that you enter in the Business Unit fields.

Current Date Select this option to use the date at the time the Journal Post processbegins to run for the Post Date for all journals in the batch.

Next Day Select this option to change the Process Date for the business units to the nextday. This option is useful when you run the Journal Post process every day andyou want to automatically change the user-defined date to the next day.

Specify Date Select this option to change the Process Date for the business units to adate that you specify and enter the date in the Specify Date field.

The system only adjusts the date to a working calendar day if thereis a working calendar defined. You define your working calendaron the Business Calendar page.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining Accounting Calendars,” Defining Business Calendars

Marking Journals for PostingAccess the Mark Journals for Posting page.



Mark Journals for Posting page

The system groups journals by Business Unit, Ledger Group, accounting Year/Period, Source, and JournalDate From/To, which means that you must select these values at the prompt. You can leave JournalID blank or use a wildcard (%) value. Source must be populated but you can use % to return journalswith all source values. You can also use a Wildcard (%) for Business Unit.

Post Selected Journals Click to access the Post Journals Request page.

Note. For better efficiency, we recommend that you schedule abackground process for journal posting.

Journal ID Click the link under Journal ID to drill down to the detail contained in a journal.

See Also


Running the Journal Post ProcessAccess the Post Journals Request page.



Post Journals Request page

Skip Open ItemReconciliation

Select to postpone closing the open items and to skip item reconciliationuntil after the journal is posted. Selecting this option can save timeduring journal posting. You can run the Open Item Reconciliationprocess (GLPPOITM) separately at a later time.

Skip Summary LedgerUpdate

Select to postpone updating the summary ledger balances. You can runthe Summary Ledger process (GLPSMAIN) at a later time. Selectingthis option can save time during journal posting.

See Also

Chapter 11, “Using Open Item Accounting,” page 223

Chapter 7, “Optimizing General Ledger Performance,” page 79

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Generating or Updating a Summary Ledger

Checking the Status of Posting RequestsAccess the Message Log page.

Enables you to view the status of the posting request and details of any messages that occur during the processing.



Unposting JournalsThis section provides an overview and discusses how to:

• Mark journals for unposting.

• Change the unpost journal entry date.

Page Used to Unpost Journals


Mark Journals for UnpostingJOURNAL_UNPOST_MRK General Ledger, Journals,Process Journals, MarkJournals for Unposting

Mark journal entries that youwant to unpost. Displaythe Unpost Date if allowdifferent unpost date isenabled on the Business UnitJournal Options page.

Marking Journals for UnpostingAccess the Mark Journals for Unposting page.

Mark Journals for Unposting page

Business Unit, LedgerGroup, Year, Adj. Periods(adjustment), Period,Source, Journal ID,Journal Date From,Journal Date To, JournalClass

Enter the criteria that you want to apply to the journals to unpost (reverse).

You can leave Journal ID blank or use a wildcard (%) value. You canalso use a Wildcard (%) for Business Unit or Source.

This applies only to anchor journals. Non- anchor InterUnit journals canonly be unposted (or posted) from their anchor journal.



ChartField SearchCriteria: Field Name,ChartField Value

Enter the names and values of the ChartFields on the journals thatyou want to mark to unpost (reverse). Add the number of ChartFieldsthat you want to include in the search.

Unpost Selected Journals Click to open the Post Journals Request page where you run the JournalPost process (GLPPPOST) to unpost journals you selected.

Select Journals to Unpost Select the Process check box for the journals that you want to unpost.Change the Unpost Date if you want it to be different than the journal date.You can click each Journal ID to review the journal’s details.

If the unpost period (Transaction Type ’UNP’) is closed for the businessunit, the Process check box will be unavailable for selection.

Journal ID To view journal details, click the individual journal ID to access theJournal Inquiry page. Click the Show All check box or enter fromor through lines and click the Drill to Journal Lines button to viewjournal lines on the Journal Lines Inquiry page.

Note. The Unpost Date field can be modified only if you selected the Allow DifferentUnpost Date on the business unit’s Journal Options page.

See Chapter 3, “Defining Your Operational Structure,” Defining Journal ProcessingOptions for a Business Unit, page 30.

Correcting Journal ErrorsThis section provides an overview and discusses how to:

• Use the journal suspense correction option.

• Select a journal line display.

• Review journal ChartField errors.

• Change ChartField values.

• Change reversal information for correction journal

• View errors for suspense journal correction lines.

• Inquire on suspense cross references.

• Post and unpost suspense and correction journals.

• Unlock a journal process instance



See Also



Pages Used to Correct Journal Errors


Journal Suspense CorrectionJRNL_SUSP_CORR General Ledger, Journals,Suspense Correction, CorrectSuspense Entries, JournalSuspense Correction

Use the Journal SuspenseCorrection page to create ajournal to correct and reversethe suspense lines on aposted suspense journal.Select a suspense journalfrom the list of all suspensejournals that have a journalstatus of Posted to Ledger(s).The process will not allowyou to select an unpostedsuspense journal.

Journal Line Template JOURNAL_LN_S_TMP General Ledger, Journals,Suspense Correction, CorrectSuspense Entries and clickthe Template List link

Use the Journal LineTemplate page to select ajournal entry template thatspecifies the columnsthat you want to displayon the Journal SuspenseCorrection page. You definethe template on the JournalEntry Template page.

Journal ChartField Errors JRNL_SUSP_CFE_SEC General Ledger, Journals,Suspense Correction, CorrectSuspense Entries and clickthe Correct ChartField Errorslink (The link appears only ifthe suspense journal has editsuspense lines.)

Use the Journal ChartFieldErrors page to correctindividual ChartField valuesthat are in error.

Change ChartField Values JRNL_SUSP_CF_SEC General Ledger, Journals,Suspense Correction, CorrectSuspense Entries and clickthe Change ChartFieldValues link

Use the Change ChartFieldValues page to change aChartField value for multipleedit correction lines globallyon the Journal SuspenseCorrection page.



Page Name Object Name Navigation UsageJournal Suspense CorrectionReversal

JRNL_SUSP_CORR_RVR General Ledger, Journals,Suspense Correction, CorrectSuspense Entries and clickthe Reversal link. (The linkappears only if the suspensejournal has a reversal codeother than "Do Not GenerateReversal" and the user hasauthorization to Change Dateon Correction Journals as setup on User Preferences −General Ledger page.)

Use the Journal SuspenseCorrection Reversalpage to enter the reversalinformation for correctionjournal.

Errors JRNL_SUSP_ERRS General Ledger, Journals,Suspense Correction, CorrectSuspense Entries, and selectthe Errors tab

Use the Journal SuspenseCorrection Errors page tosee the error message for ajournal line. Click the Errorsfor any line on the JournalSuspense Correction page.

Review Suspense CrossReference

JRNL_SUS_CROSS_REF General Ledger, Journals,Suspense Correction, ReviewSuspense Cross Ref, ReviewSuspense Cross Reference

PeopleSoft GeneralLedger uses a JournalHeader Sibling table(JRNL_HDR_SIBL) to linkthe suspense journal and itscorresponding correctionsjournal. Use the ReviewSuspense Cross Referencepage to view the connectionbetween the two journals;you can review bothjournals’ status by click onJournal Status and SuspenseJournal Status hyperlinks.

Journal Unlock JRNL_EDIT_LOG General Ledger, MonitorBackground Processes,Journal Unlock

Use to unlock journals ina process instance thatterminated abnormally.

Using the Journal Suspense Correction OptionAccess the Journal Suspense Correction page.



Journal Suspense Correction page 1 of 2

Journal Suspense Correction page 2 of 2

Journal ID Defaults toNEXTand will generate the next available journal numberwhen you save the journal. If you do not want to use the default, entera unique journal ID for the correction journal.

Date Defaults to the date of the suspense journal. Only authorized users can changethe correction journal date as well as the reversal information if the suspensejournal has a reversal code other thanDo Not Generate Reversal.

Long Description Defaults toCorrection of Suspense Journalfollowed by the Journal ID of thesuspense journal you’re correcting. You may change this description if desired.

Template List Click to open the Journal Line Template page that enables you toselect a template that specifies which columns you want to displayin the Correction Journal Lines grid.

Correct ChartField Errors Click to open the Journal ChartField Errors page where you changethe ChartField values in error.

Change ChartFields Values Click to open the Change ChartField Values page where you can changea ChartField value globally on multiple edit correction lines.

Reversal Click the link to open the Journal Suspense Correction Reversal page whereyou can change the reversal information for correction journal.

Correction Journal Lines

The Correction Journal Lines grid displays the journal lines for the suspense journal that need to be corrected.The system generates edit and amount correction lines with the ChartFields and amounts from the journalline(s) marked in error. Use these correction lines to correct ChartField and amount errors.



Note. Correction journal lines for secondary ledgers arenot displayed in the grid if the suspensejournal is created with the KLS (Keep Ledgers in Sync) option selected.

When you first open the Journal Suspense Correction page, the amount correction line(s) are atthe top of the scroll area, followed by balance correction line (s) and edit correction line (s). Noreferences exist in the suspense journal for the balance correction line(s).

Ref Ln # (reference line number) displays the line number that contains an amount error or an edit error in thesuspense journal. The reference line number will always be blank for the balance correction lines.

Click Errors for any line to open the Journal Suspense Correction − Errors page thatshows the error log for the line.

When you save your work, the system creates a correction journal that contains the newcorrection lines. The system also generates the reversing suspense lines for the suspensejournal. You won’t see these lines displayed in the grid.

Important! When you create a correction journal, you must determine on your own whether the lines arecorrect or incorrect. If necessary, you can make further changes to the corrected journal before you run theJournal Edit process (Application Engine process GL_JEDIT) and the Journal Post process (GLPPPOST). But,you must make these changes from the Journal Entry - Lines page because the system changes the suspensestatus of the suspense journal to 2 when you save your correction journal. The Journal Suspense Correctionpage will not let you reenter the page for a suspense journal if its correction journal already exists.

If you have not run the Journal Post process (GLPPPOST) for the correction journal and you decide you wantto start over, select the Delete Journal option in the Process field on the Journal Entry - Lines page to delete thiscorrection journal. The system will update the suspense status of the suspense journal back to1, and you canreturn to the Journal Suspense Correction page to create a new correction journal for the same suspense journal.

Note. Correction journal is a non-interunit journal when created. Like journals created by Journal Entry -Lines page, system still populates correction journal’s IU System Transaction Code (IU_SYS_TRAN_CD)& IU Transaction Code (IU_TRAN_CD) but based on the suspense journal’s values. If the suspensejournal does not have these two values, interunit lines are not generated for the correction journal evenif it is modified using the Journal Entry - Lines page to an interunit journal.

Selecting a Journal Line DisplayAccess the Journal Line Template page.

Journal Line Template page

Selected Select to indicate that you are currently using the template when it ischecked. To use a different template, select another line.



Template Type Identifies the users who would use the template. For example, anyone coulduse anAll template type. The Template ID is the name for the template.

Default If selected, the system uses the columns selected as the default whenyou open the Journal Suspense Correction page. You can only change thedefault on the Journal Entry Template − Template page.

Note. The ChartField column check boxes that display on the Journal Line Template page areautomatically selected and cannot be changed. If you want to display different columns, select thetemplate that meets your requirements or create a new journal entry template.

Reviewing Journal ChartField ErrorsAccess the Journal ChartField Errors page.

Journal ChartField Errors page

Correct ChartField Errors This link appears on the Journal Suspense Correction page only ifthe suspense journal has edit suspense lines.

Error Count Indicates the number of lines that contain the ChartField value in error.

Field Name Indicates the ChartField whose value is in error.

Field Value Displays the incorrect ChartField value.

Change to Enter the correct ChartField value.

Selected Click to select the ChartField values that you want to update onthe Journal Suspense Correction page.

Changing ChartField ValuesAccess the Change ChartField Values page.



Change ChartField Values page

Field Name Name of each ChartField.

Field Value Enter the ChartField value that you want to change.

Change to Enter your new ChartField value.

Selected Select this check box to replace all occurrences of the ChartField valueon the Journal Suspense Correction page.

Changing Reversal Information for Correction JournalAccess the Journal Suspense Correction Reversal page.



Journal Suspense Correction Reversal page

Enter reversal information for correction journal when the suspense journal reversal codeis not Do Not Generate Reversal.A Reversal journal for a suspense journal never goes tosuspense, so you need only to correct the suspense journal.

Beginning of Next Period Creates a reversing entry dated the first business day of the next accountingperiod. It uses the Holiday List ID that you assigned to the business unit on theGeneral Ledger Definition − Definition page to determine the first businessday. If the business unit is not assigned a Holiday List ID, the reversingentry will be dated the first day of the next accounting period.

If the journal is an adjusting journal, the reversing entry will be dated the firstbusiness day of the first accounting period of the next fiscal year.

End of Next Period Creates a reversing entry dated the last business day of the next accountingperiod. It uses the Holiday List ID that you assigned to the business unit on theGeneral Ledger Definition − Definition page to determine the last businessday. If the business unit is not assigned a Holiday List ID, the reversingentry will be dated the last day of the next accounting period.

If the journal is an adjusting journal, the reversing entry will be dated the lastbusiness day of the first accounting period of the next fiscal year.

Next Day Creates a reversing entry dated the next business day. It uses the Holiday ListID that you assigned to the business unit on the General Ledger Definition −Definition page to determine the next business day. If the business unit is notassigned a Holiday List ID, the reversing entry will be dated the next day.

Adjustment Period Creates a reversing entry to the adjustment period you select. When you selectthis option, enter both the Adjustment Period and the Reversal Date.

On Date Specified By User Enables you select any date in the calendar. When you select thisoption, enter the Reversal Date.

Adjustment Period When you select this option, enter a value in this field. Click inthe drop-down list to display a list of valid adjustment periods(as defined on the Detail Calendar).



Reversal Date When you select Adjustment Period or On Date Specified By User option,enter a value in this field. The Reversal Date is used to populate the journaldate and fiscal year of the reversing entry. If you specify a reversal datethat is before the journal date or a date on a nonworking day and there is aHoliday List ID assigned to the business unit, you will receive an errormessage. The system will not reset the reversal date, and you must re-enter adate that is after the journal date and is a working day.

Viewing Errors for Suspense Journal Correction LinesAccess the Errors page.

Journal Suspense Correction - Errors page

This page displays information about the ChartFields and Amount errors on the suspense journal.

Error Type Indicates the type of error, which can beChartField error,ComboEdit error, Amounterror, orUnknown.

Line # (line number) Indicates the number of the Ref Ln # on the Journal Suspense Correctionpage with the error. It shows the Field Name for the ChartField in error.It also displays the Msg Set (message set number) that contains the errormessage, the Msg (message number), and Message Text. Click the linenumber to return to the Journal Suspense Correction page and placeyour cursor where you need to make the correction.

Inquiring on Suspense Cross ReferencesAccess the Review Suspense Cross Reference page.

Review Suspense Cross Reference page

Specify a combination of Unit, Correction Journal ID, and Date for your correctionjournal search criteria or leave Journal ID

Search Click to view the correction journals that meet your search criteriaand its corresponding Suspense Journal. Click Journal Status/SuspenseJournal Status hyperlink to transfer to the Review Journal Status -Journal Lines page. It opens a new window, and from there you canview suspense/correction journal line information.



Journal Status Click link to access Review Journal Status page for this journal ID.

Suspense Journal Status Click link to transfer to the Review Journal Status for the suspense journal ID.

Posting and Unposting Suspense and Correction JournalsBecause a link exists between a suspense journal and a correction journal, it is important tounderstand the rules for posting and unposting these journals.

Suspense Journals

The Journal Post process (GLPPPOST) uses the suspense journal status to determine how to process the journals.

1 Unpost is allowed. The correction journal has not been created.

2 Unposting isnot allowed. The correction journal is created, but not yet posted.

3 Unposting is allowed. The process also unposts the correction journal. An entrywill be inserted into the journal Header Sibling table with the unpost seq of1.

Correction Journals

When you post a correction journal, the system updates the suspense status to3 on the suspense journal. Youcannotunpost a correction journal. Instead, you unpost the suspense journal, thereby unposting both journals.

If the original journal had a reversal journal, the correction journal will also have a reversal that iscreated when posting the correction journal. All four journals are unposted together.

Unlocking a Journal Process InstanceAccess the Journal Unlock page.

Journal Unlock page

PeopleSoft General Ledger uses application locking when you run batch processes. When a generalledger process is processing a journal, it locks the journal so that no other process can access it. Aprocess automatically turns the journal lock flag on and off to lock and unlock the journal duringthe process. If a process terminates abnormally, the journal may remain locked. We enable you tounlock journals in a process that failed by using the Journal Unlock page.

The page displays the ID of the User who ran the process that terminated abnormally.

The Processes List grid displays a list of processes that the user has run.



For each run of a process, it displays the Process Instance number and the Run Control ID. The ProcessOrigin indicates how the process was initiated, and it has the following possible values:

Other GL Application Another general ledger process, such as Allocations (FS_ALLC),called the process to start it.

Other The process was initiated from an operating system command line.

Process Scheduler A process scheduler definition initiated the process.

Remote Call The process was initiated by an individual taking an action on a page.

The Last Update DateTime indicates the last date and time that the process made an update to the message log.

Select Marked for each process instance whose journals you want to unlock, and click Unlock button.

Producing Journal ReportsTo run a report, select it from its menu and enter the necessary parameters. After entering thereport parameters, you use Process Scheduler to actually run the report. Process Schedulermanages the processes, tracks the status, and generates the report.

To modify standard reports, create your own reports, or change the report output format,a variety of reporting tools are available.



Pages Used to Produce Journal Reports


Posted Journal SummaryReport

RUN_GLS7009 General Ledger, Journals,Process Journals, PostedJournal Summary Report

Use to define parameters forthe Posted Journal Summaryreport (GLS7009) This SQRreport provides the ability toreport on journals postedduring a specific run ofthe Journal Post process.The Journal Post processupdates all journals postedwith the value of the ProcessInstance. The ProcessInstance is part of the searchcriteria used by the PostedJournal Summary report.

Journal Edit Errors Report RUN_GLS7011 General Ledger, Journals,Process Journals, JournalEdit Errors Report

Use to specify the runparameters for theJournal Edit ErrorsReport (GLS7011). ThisSQR report lists detailedinformation on journaledit errors.

Suspended Activity Report RUN_GLS7015 General Ledger, Journals,Suspense Correction,Suspended Activity Report

Provides detailedinformation on suspendedjournals. (Refer to GLS7011for its functions.) TheSuspended Activity reportlists all journal activities thatare suspended.




CHAPTER 11

Using Open Item Accounting

This chapter provides an overview of open item accounting and discusses how to:

• Set up an open item prompt table.

• Enter and process open item transactions.

• Reconcile and close open item balances.

Understanding Open Item AccountingOpen item accounting in PeopleSoft General Ledger enables you to define, control, and maintain sub-ledgerdetail for selected balance sheet accounts used in open item transactions. You can track these open itemtransactions until they are resolved and the balance of the open item account is zero. A common exampleof open item accounting is the tracking of employee draw account transactions.

PrerequisitesBefore you can use open item accounting you must:

• Identify open item accounts.

• Specify an open item ledger.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Entering and Maintaining ChartField Values


Open Item Accounting in PeopleSoft General LedgerUse PeopleSoft General Ledger open item accounting to:

• Create one or more open item accounts to track numerous open items.

• Reconcile open item balances either by using the Open Item page or by using the PS/GLOpen Item Reconciliation, GLPPOITM, process.

• Display open item balances for each open item account online in the Open Item Status page.


Using Open Item Accounting Chapter 11

• Generate reports on each open item’s status and transaction detail.

Common Open Item TerminologyThese terms are common to open item accounting in PeopleSoft General Ledger:

Open Item Account A ChartField account, normally balance sheet accounts, used for openitem accounting, such asEmployee Advances.

Open Item Key The identifying or search key for open items in an open item account. Foran employee advances account, the Open Item Key field typically is theemployee ID or social security number. This implies that any journal entrythat posts to the employee advances account also carries an employee ID inthe Open Item Key field. This search key is required by the system.

Open Item Each transaction that affects an open item account remains an open item untilthe balance of all transactions with a given open item key equals zero. Forexample, the first open item in the employee advances account is the issuanceof an advance. payment against the initial advance become open items until afinal payment brings the balance for a given employee ID to zero. When thattransaction is posted, all open items for the employee ID are closed.

Closed Item Transactions for an open item key become closed items when the balanceof the open item key transactions equals zero.

Tolerance Amount Indicates that PeopleSoft General Ledger should close transactions in whichopen items do not sum up to zero, provided the open item balance fallswithin this specified tolerance amount. This only applies to open items youreconcile manually (online). The system does not apply a tolerance amount foropen items reconciled through background (batch) processing.

Open Item Prompt TablesYou can add an Open Item Prompt Table to perform an online lookup of valid open item keys.

This new prompt table is a SQL view that you create by selecting two fields from the Open Item Edit Record,as defined with the Open Item Account, in PeopleTools Application Designer. The two fields are:

• The Open Item Edit Field that you must rename to OPEN_ITEM_KEY in your new SQL view.

• A description field that is informational only.

Note. Before performing modifications, complete the PeopleTools classes to learn to usethe PeopleTools Application Designer and its associated database tools. Completion of thePeopleCode and SQL/SQR classes is recommended.

See Also

PeopleTools PeopleBook: PeopleSoft Application Designer

Reconcile and Close Open Item BalancesYou can reconcile and close open item balances using one of the following methods:


Chapter 11 Using Open Item Accounting

• When you leave the Skip Open Item Reconciliation check box on the User Preferences −General Ledger page blank and post your open item transaction online, the transactionsare reconciled and closed during the posting process.

• When you do not select theSkip Open Item Reconciliationcheck box on the Request Posting − RunJournal Post page, the transactions are reconciled and closed during the posting process.

• When you access the Reconcile Open Items - Open Item Recon (reconciliation) page and run thePS/GL Open Item Reconciliation process as a background (batch) process.

• When you access the Update Open Items − Open Item page, you can select, reconcile, and close openitem transactions manually. This option is normally used for open items with balances that do not equalzero. The entries you close must still balance or meet the reconciliation tolerance amount.

Setting Up an Open Item Prompt TableThis section describes how to create an open item prompt table.

Creating an Open Item Prompt TableTo create an Open Item Prompt Table:

1. Create a new record using the Application Designer.

2. Change the record type to SQL View.

3. Insert OPEN_ITEM_KEY field into the record. Make it a key, search key, and list box item.

4. Insert a DESCR or NAME field to the record. Make it an alternate search key and list box item.

5. Enter the View text:

select [open item edit field], [description or name field]

from [open item edit record]

6. Save the View.

7. Use Build menu option to create the view.

You then go to the Open Item Account and enter this SQL view name as the Prompt Table for this account.

See Also

PeopleTools PeopleBook: PeopleSoft Application Designer

Entering and Processing Open Item TransactionsIn this section, we discuss how to:

• Create open item transactions.



• Process open item transactions.

Use the Create Journal Entries menu option to enter and process open item transactions. Edit and postthe transactions online or use the Process Posting option on the Process Journals menu.

Note. You cannot use open items with accounts that are VAT enabled.

See Also


Chapter 10, “Processing Journals,” Understanding Journal Processing, page 189

Pages Used to Enter and Process Open Item Transactions


Journal Entry −Header JOURNAL_ENTRY1 General Ledger, Journals,Journal Entry, Create JournalEntries

Used to identity the LedgerGroup that contains theLedger used to track openitems.

Journal Entry-Lines JOURNAL_ENTRY2_IE Journals, Journal Entry,Create Journal Entries

Used to create open itemtransactions by selecting theopen item account and theopen item key. You can alsoperform on-line editing andposting on this page.

Creating Open Item TransactionsAccess the Create Journal Entries − Header page.

To create open item transactions:

1. Select the ledger group that contains the open item ledger.

2. Access the Journal Entry − Lines page.

3. On line 1 enter or select the open item transaction parameters including the open itemaccount, the amount, and the open item key.

4. Add line 2 of the transaction.

5. Save the transaction.

Note. If you did not enter or if you entered an incorrect open item key, a message displays when you addanother line or attempt to save the transaction. Also, an open item account cannot be VAT enabled. Ifyou have an existing open item account that is VAT enabled, access the account in Define ChartFields,Define Values — ChartField Values and remove the check mark from the OpenItem Account checkbox, or change this account from a VAT Account to a Non-Vat Related account.

Processing Open Item TransactionsYou can edit or post open item transactions on-line or in batches.



Note. If you select the Post Journal Process on the Creating Journal Entries - Lines page, the system checks theUser Preferences − General Ledger page and uses the value specified for the Skip Open Item Reconciliationflag. If the check box is selected, the Open Item Reconciliation process is bypassed during the posting processand the open items are posted but not reconciled. However, if you run the Journal Post process (GLPPPOST)from the Journal Post − Request page, you must select the Skip Open Item Reconciliation field on the page.

See Also


Reconciling and Closing Open Item BalancesThis section describes how to:

• Use the PS/GL open item reconciliation process (GLPPOITM).

• Use the manual open item reconciliation and close process.

• Review reconciled open items.



Pages Used to Enter Open Item Transactions


Process Reconciliation -Open Item Recon

GL_OI_RECON_REQ General Ledger, Open Items,Process Reconciliation

Closes open itemsautomatically. The items thatremain open appear on theOpen Item and the OpenItem status pages after theposting process. You mustreconcile these remainingopen items manually.

Open Item GL_OPEN_ITEM_SUM General Ledger, Open Items,Maintenance, Open Item

Displays at the summarylevel a list of open itembalances and associatedChartFields that you canreconcile or re-open.

Open Item Transaction GL_OPEN_ITEM_DET General Ledger, Open Items,Maintenance, Open Itempage. Select and click anopen item key numberto access the Open ItemTransaction page.

Displays open itemtransaction details tothat you can reconcileindividually, change theopen item key name andre-open an item.

Review Status Online - OpenItem Status

GL_OPEN_ITEM_SUM General Ledger, Open Items,Review Status Online −Open Item Status

Displays status of openitems. You cannot reconcile,re-open any items, or edit theopen item key.

Open Item Detail GL_OPEN_ITEM_DET General Ledger, Open Items,Review Status Online, OpenItem Status. Click the OpenItem Key number to accessthe transaction detail.

Displays status of open itemtransaction details. Youcannot reconcile re-openany items or edit the openitem key.

Using the PS/GL Open Item Reconciliation process (GLPPOITM)Access the Process Reconciliation − Open Item Recon page.

To reconcile and close open items using the PS/GL Open Item Reconciliation process:

1. Enter the run parameters.

2. Run the PS/GL Open Item Reconciliation process.

Note. The system uses Reconciliation Tolerance amounts solely for manual reconciliation. The PS/GLOpen Item Reconciliation process only closes open item transactions with a zero balance.

Using the Manual Open Item Reconciliation and Close ProcessAccess the Maintenance − Open Item page.



Open Item Maintenance page (1 of 2)

Open Item Maintenance page (2 of 2)

This Maintenance option enables you to:

1. Enter open item criteria.

2. Reconcile and close open items at the summary level.

3. Reconcile and close open items at the detail level.

4. Reconcile and close multiple currency rows with the same Open Item Key

5. re-open reconciled and closed open items



Entering Open Item Criteria

Enter the criteria to list your open item balances. In the Inquire field, selectopen, closed,or bothto display the status of Open Item Balances at the summary level.

Note. If you do not know the Open Item Key or want to select all open items for the ChartFields youspecify, leave the Open Item Key field blank and the system selects all open items.

Reconciling and Closing Open Items at the Summary Level

To reconcile and close open item balances at the summary level:

1. Click Reconcile.

If the summary rows net to a zero balance or meet your tolerance amount test, the system closes allopen item detail lines contained within the selected summary rows and issues reconcile numbersand date closed values for the selected rows and their detail lines.

2. Select one of the these Reconcile options.

Reconcile Each RowSeparately

The system closes each summary row individually and assigns adifferent reconcile number and date closed.

Reconcile Selected RowsAs One

The system closes all the summary rows as a group, moving fromone row to the next and assigning all the selected rows the samereconcile number and date closed.

Note. To reconcile multiple summary rows simultaneously, all the summary rows musthave thesameOpen Item Key and ChartField values

Two read-only fields:

Selected Displays the total of all of the selected Open Item Balances rows. Thistotal changes each time you select another row.

Total Displays the Open Item Balance total of all the rows on the page.

Note. Tolerance amounts are used solely for manual reconciliation. The background processcloses only open item transactions that have a zero balance.

Reconciling and Closing Open Items at the Detail Level

You can close detail lines as a group or you can select specific detail lines to close for an Open ItemKey. The total balance of the detail lines you want to close must have a zero sum balance or fall withinthe reconcile tolerance amount specified when you set up your open item accounts.

To reconcile and close detail lines as a group:

1. Click the Open Item Key to display the open item transaction detail lines.

2. If the Open Item Key has more than one transaction detail line, you can select eachof the lines and reconcile them as a group.



If all the detail lines have a sum balance of zero or meet the tolerance amount, the system closes all openitems for that key and issues a reconcile number for all detail lines. The reconcile number identifies thereconciled open item, distinguishing it from all other closed items. The system also assigns a closed datevalue to all detail lines, which is the most recent journal date among the detail lines of the open item key.

To reconcile and close selected detail lines, select the specific detail lines that youwant to close and click Reconcile.

The system closes only the selected open items and assigns these lines the same reconcile number and dateclosed value. When you close the remaining detail lines, the system assigns them a new reconcile number anddate closed value. Both reconcile numbers and date closed values display on the corresponding summary row.

Note. You can make corrections to open item key values even after you have posted the journal becauseyou are changing a key related specifically to the open item line and not to the journal line.

Reconciling and Closing Multiple Currency Rows with the Same Open Item Key

You can close multiple rows with different transaction currencies and the same open item key at thesame time. The system groups open item lines for each currency as separate rows at the summary level.If all ChartFields are the same and the selected summary rows have either a zero sum balance or meetthe reconcile tolerance amount, you can select and close these rows as a group.

Re-opening Reconciled and Closed Items

You can re-open reconciled and closed items by:

• Selecting the individual open item lines with the same reconcile number and clicking Re-Open.

• Clicking Select All and then re-open to re-open all the lines.

Reviewing Reconciled Open ItemsAccess the Review Status Online − Open Item Status page to:

• Review open item balances, or review closed open item transactions.

• Search by Chartfield values, Open Item Keys, Reconciliation Number, or Document Sequence Number.

• Change the Inquire option toClosedto display reconciled items.

• Specify Closed From and Closed To date range. If you do not specify these dates,the system uses the current system date.

• Use the Reconcile Nbr (number) field to search for all reconciled open items closed by this reconcile number.




CHAPTER 12

Using Inter/Intraunit Processing in PeopleSoftGeneral Ledger

This chapter provides an overview of inter/intraunit processing and discusses how to:

• Use the Journal Edit Application Engine process (GL_JEDIT) to initiate the Inter/IntraunitProcessor Application Engine process (IU_PROCESSOR).

• Generate suspense correction journal lines for inter/intraunit transactions.

• Copy inter/intraunit journals.

• Create inter/intraunit journal entries.

• Create inter/intraunit allocation journals.

• Perform inter/intraunit consolidations.

• Import inter/intraunit transactions using a flat-file journal import.

• Import inter/intraunit transactions using a spreadsheet journal import.

Understanding Inter/Intraunit Processing inPeopleSoft General Ledger

PeopleSoft General Ledger enables you to use a minimal number of journal entry lines to record atransaction between related entities. You do not have to enter all the lines that are required to fullybalance the entry. Several processes handle unbalanced entries, such as:

• Journal entry.

• Spreadsheet journal entry.

• Flat-file journal import.

• Inter/Intraunit allocations.

For each of these processes, the Journal Edit process initiates the Inter/Intraunit Processorprocess to complete the entries automatically.

Inter/Intraunit accounting occurs at the general ledger business unit level, independent of theindividual product or feeder system business unit definitions.


Using Inter/Intraunit Processing in PeopleSoft General Ledger Chapter 12

Inter/Intraunit transactions are balanced by general ledger business unit and are also balanced by anyof the ChartFields that can be designated as balancing ChartFields, such as the Fund ChartField orthe Department ChartField. Use the Ledger Groups - Balancing page to determine which of theseChartFields are balancing ChartFields according to your accounting requirements.

You can use inheritance or due-to and due-from balancing to achieve inter/intraunit balancing.

Inter/Intraunit due-to and due-from entries are generated with respect to an anchor value. Youdetermine the anchor ChartField value when making intraunit journal entries. The anchor valuefor interunit entries is the business unit entered on the journal header.

PeopleSoft General Ledger also supports interunit accounting among general ledgerbusiness units with different base currencies.

You can set up direct interunit accounting or indirect interunit accounting. If you use direct interunitaccounting, the general ledger business units use their own intercompany accounts to record theinterunit transaction. If you use indirect interunit accounting, the general ledger business unitsuse the intercompany accounts of the other business units involved.

Note. If you are using alternate accounts, you must use direct interunit accounting.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Using Interunit andIntraunit Accounting and ChartField Inheritance”

Use of the Journal Edit Process to Initiate theInter/Intraunit Processor ProcessThe Journal Edit process calls the Inter/Intraunit Processor process to generate balancing due-to anddue-from journal lines after secondary ledger lines are created, currency is translated, value-added tax ismaintained, the Transaction Set Editor has completed validating the transactions, and edit and amountsuspense processing is performed. After calling the Inter/Intraunit Processor process, the Journal Edit processcalls Entry Event Processor Application Engine process (FS_EVENTGEN) to process the entry events.It then checks the balancing of the journal and performs balance suspense related processing.

See Also


Generation of Suspense Correction Journal Lines forInter/Intraunit TransactionsThe Journal Edit process creates edit and amount suspense correction journal lines before callingthe Inter/Intraunit Processor process. Edit and amount suspense correction lines are created beforethe Inter/Intraunit Processor process creates balancing entries.

See Also

Chapter 10, “Processing Journals,” Using the Journal Suspense Correction Option, page 212


Chapter 12 Using Inter/Intraunit Processing in PeopleSoft General Ledger

Inter/Intraunit Journal CopyingThe PeopleSoft system supports copying of inter/intraunit journal entries.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Copying Journal Entries , page 154

Creating Inter/Intraunit Journal EntriesThe predefined PeopleSoft General Ledger system transaction definition GLJ (general ledger journal)enables you to enter and process entry events with inter/intraunit transactions.

The definition GLJ enables you to map multiple transaction fields to create additional subsets or categorizationsof an inter/intraunit transaction. The transaction code value appears by default from the system transactionmap for GLJ. You can override the default by entering transaction codes on the Journal Entry - Header page.

You can organize inter/intraunit journal entries in inter/intraunit groups and assign anchor business unitand anchor ChartField values that the system uses to create balancing entries.

The PeopleSoft system provides several balancing methods, and you can assign affiliateChartFields to manage inter/intraunit entries.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Configuring ChartFields,”Using Standard ChartField Configuration

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Choosing Affiliate ChartField Values

Chapter 8, “Making General Ledger Journal Entries,” Creating Inter/Intraunit Journal Entries, page 143

Chapter 23, “Using Entry Events in PeopleSoft General Ledger,” page 477

Creating Inter/Intraunit Allocation JournalsWhen you allocate business units in the pool to other business units, the Allocation process creates interunitjournals and calls the Journal Edit process to create the balancing due-to and due-from journal lines.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Processing Allocations,”Setting Up Interunit and Intraunit Allocations

Performing Inter/Intraunit ConsolidationsThe PeopleSoft system supports inter/intraunit consolidations and the use of affiliate ChartFields.


Using Inter/Intraunit Processing in PeopleSoft General Ledger Chapter 12

See Also

Chapter 16, “Performing Financial Consolidations,” Selecting an Approach to Inter/IntraCompany Transactions, page 316

Chapter 16, “Performing Financial Consolidations,” Consolidating on a ChartFieldOther Than Business Unit, page 316

Importing Inter/intraunit Journals Using a Flat-File Journal ImportThe PeopleSoft system supports inter/intraunit flat-file journal import.

See Also


Importing Inter/Intraunit Journals Using a SpreadsheetJournal ImportThe PeopleSoft system supports inter/intraunit spreadsheet journal import by including the IU Group(inter/intraunit group) field and the IU Anchor (inter/intraunit anchor) field.

See Also



CHAPTER 13

Processing Value Added Tax (VAT) Transactionsin PeopleSoft General Ledger

This chapter provides an overview of processing VAT transactions in General Ledger and discusses how to:

• Set up VAT options and defaults for PeopleSoft General Ledger processing.

• Create and process journals with VAT.

• Import VAT data from third-party systems.

Understanding PeopleSoft General Ledger VATSetup and Processing

PeopleSoft accommodates a number of methods for calculating value added taxes based on the countrieswhere your organization is either located or with which it conducts business. You can set up all of yourVAT Defaults and other VAT information in Setup Financials/Supply Chain, Common Definitions, VATand Instrastat, Value Added Tax for each of your PeopleSoft applications. You must set up VAT forPeopleSoft General Ledger at the business unit, journal source, and account ChartField levels. Each ofthese levels is represented by a VAT driver created by PeopleSoft. You can set up the VAT defaults forPeopleSoft General Ledger in a central VAT location by selecting the appropriate VAT driver:

• Account ChartField

• Journal Source

• GL Business Unit

When you click the VAT Defaults link on the General Ledger Business Unit Definition -VATDefaults page, the Journal Source Definition page, and Account ChartField page, the VAT DefaultsSetup page based on one of the VAT Driver for General Ledger.

For example, the when you click the VAT link on the General Ledger Business Unit - VAT Defaults page, theVAT Driver for the VAT Defaults page is BUS_UNIT_TBL. When you select the VAT link on the Accountpage, the VAT Driver for the VAT Defaults page is GL_ACCOUNT_TBL. Finally, if you select the VAT linkon the Journal Source Definition page for Online Journal Entries (ONL) the VAT Driver is SOURCE_TBL forthe VAT Default page. Each of the different VAT Drivers determine what will appear in the VAT Defaults page.

To process PeopleSoft General Ledger transactions, you must set the defaults and parameter controls that applyto VAT at the business unit, journal source, and account levels. The objective is to calculate and create avariety of VAT accounting entries to record not only the tax on goods and services, but also simultaneouslyrecord the recoverable, non-recoverable, and rebate portions of the VAT at the journal line level.


Processing Value Added Tax (VAT) Transactions in PeopleSoft General Ledger Chapter 13

This section presents an overview of:

• VAT default and override relationships in PeopleSoft General Ledger.

• VAT setup and defaulting for PeopleSoft General Ledger.

• VAT transaction entry and processing in PeopleSoft General Ledger.

PrerequisitesBefore you process VAT transactions in PeopleSoft General Ledger:

• ReadSetting Up Global Options and Reports, “Understanding Value Added Taxes.”

• Set up your VAT environment.

• If you intend to create an allocation journal that includes VAT processing in the journal edit, clearthe ByPass Vat Processing check box on the Output Options page. The system then recognizes theVAT Account flag, calculates VAT and generates additional VAT accounting lines where appropriate.Be careful when using this feature in a multi-level allocation because the system may generateaccounting entries more than once for the same expense to recover VAT. To avoid this, clear theBypass VAT check box for only one-step in a multi-level allocation.

Note. Refer to the individual PeopleBooks for the subsystems that feed VAT transactions to the GeneralLedger for any unique VAT information and set up for the various applications.

See Also

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Working with Value Added Taxes (VAT)”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Processing Allocations,” Selecting Output Options

VAT Default and Override Relationships in PeopleSoftGeneral LedgerThe following diagram shows the default and override relationship of these VAT options inGeneral Ledger. Defaults set up in the VAT Entity and VAT Country, however, may overridethe business unit, journal source and account in General Ledger.


Chapter 13 Processing Value Added Tax (VAT) Transactions in PeopleSoft General Ledger

VAT Options and Default Processing Hierarchy

The hierarchy for VAT default options for PeopleSoft General Ledger is:

1. VAT Entity and VAT Country

2. Business Unit

3. Journal Source

4. Account

Which means that a VAT default options set up for the VAT entity or VAT country override VATdefault options set up a the business unit, journal source, or account levels.

If there are no VAT default options set at the VAT entity or VAT country levels, then any VAT default optionsset up at the business unit level override any VAT defaults set up a the journal source or account levels.

If there are no VAT defaults set at the VAT entity, VAT country, or VAT business unit level, then the VATdefault options set at the journal source level override the VAT default options set at the account level.

When you enter a journal line, however, overriding the VAT default options works directly in reverse:

1. Account

2. Journal Source

3. Business Unit

When entering VAT at the journal line, if you established an option value at the account level, thatvalue will override a value set at the journal source and business unit levels. Likewise, if you havenot established values at the account or journal source level, General Ledger calculates VAT using theoptions set for the business unit, VAT entity registration, or VAT country levels.



VAT Setup and Defaulting for PeopleSoft General LedgerThe VAT defaults are controlled by VAT drivers at various levels of the hierarchy and arestored in a common set of defaulting tables. Depending on the driver, you can set certainfields and override them in a lower level of the hierarchy.

There are two main components that control the VAT defaulting: the VAT Defaults Setup componentand the Services VAT Treatment Setup component. For PeopleSoft General Ledger, only VAT DefaultsSetup component is applicable. You can access this component from the common VAT menu (Set UpFinancials/Supply Chain, Common Definition, VAT and Intrastat, Value Added Tax) or from the applicableGeneral Ledger pages. If you access it from the VAT menu, the driver you select determines the fields thatdisplay. If you access it from the application pages, the component from which you are accessing determinesthe fields displayed. For example, if you access the VAT Defaults Setup page from the VAT and IntrsStatCommon Definitions menu, and select the GL Business Units (BUS_UNIT_TBL_GL) driver, you will see thesame fields as you do when you click the VAT Default link on the GL Business Unit Definition - VAT page.

These VAT user overrides are remembered:

• Service Type and/or Place of Supply Driver — a change to either will protect both.

• Reporting Country and/or Defaulting State — a change to either will protect both.

• Bank/Customer/Vendor Registration Country

• Calc on Advance Payments

• Place of Supply Country and/or Place of Supply State — a change to either, where applicable, will protect both.

• Applicability.

User overrides are reset to blank when the:

• User clicks Change Physical Nature.

• User clicks Reset All VAT Defaults.

• User leaves the component and comes back in again.

SeePeopleSoft Global Options and Reports 8.8 PeopleBook, “Working with ValueAdded Taxes (VAT),” Establishing VAT Defaults.

Understanding VAT Drivers, VAT Driver Keys, and the DefaultingHierarchy for VAT Defaults

The following table lists the VAT drivers and associated VAT driver keys in VAT default hierarchysequence from most specific to least specific for the VAT Defaults component. There are no GeneralLedger drivers that apply to the Services VAT Treatment Defaults.



VAT Driver

VATDriverKeys

PeopleSoftApplication Country State

Applicable toRegular VAT

Defaults

Applicable toServices VAT

TreatmentDefaults

AccountChartField

AccountSetID

Account

GeneralLedger

Optional Optional Yes No

Journal Source SourceSetID

Source

GeneralLedger


GL Business Unit BusinessUnit

GeneralLedger


VAT EntityRegistration

VAT Entity

Country

All Required Optional Yes No

VAT Country Country All Required(key)

Optional Yes No

VAT Transaction Entry and Processing in PeopleSoftGeneral LedgerPeopleSoft General Ledger processes VAT transactions originating from the following sources:

• PeopleSoft subsystems.

• PeopleSoft General Ledger.

• External systems.

The following diagram illustrates VAT processing in PeopleSoft General Ledger.



VAT Processing in PeopleSoft General Ledger

When you create a journal entry with VAT, the Journal Edit process calculates VAT, spreads theVAT amounts, if necessary, and, for an inclusive VAT transaction, subtracts the VAT amount fromthe journal line and then adds it back in for the journal balances.

You can also create a Standard Journal Entry (SJE) Model journal for VAT. However, JournalEdit does not perform any of the processes mentioned on the model journal. Instead, the SJEprocess copies the VAT lines to retain any user-entered information and Journal Edit processesVAT on standard journals created from the SJE process.

After creating General Ledger journal entries, you can edit and post them on-line or you can process them inbatches. You must run the VAT Transaction Loader process to load data into the VAT Transaction Table beforeyou can run the VAT Report Extract process to enable you to print VAT reports. You run the VAT TransactionLoader process based on your organization’s volume of VAT data. For example, you may only need to runthis process once each week. You can select this process each time you produce reports or schedule it to runautomatically. You then can run the VAT Report Extract process based on when you need to produce reports.

PeopleSoft delivers the General Ledger AE program GL_JRNL_IMP that you use to import VAT data to Journaltables from third party systems. Since this program directly modifies and loads data into transaction tables, adatabase administrator or someone with detailed knowledge of the physical layout of the tables should run them.You must be aware which tables are affected by these programs and run the programs at the appropriate times.

The Effects of Changing VAT Defaults

VAT Defaults are displayed in descending order of impact. When you change multiple VAT defaultsand clicks Adjust Affected VAT Defaults, specific fields will or will not be adjusted. You should workfrom the top down to the bottom, clicking Adjust Affected VAT Defaults at the appropriate time(s) toavoid adjustments to VAT Defaults that you overrode but not did not memorize.



For example, if you override Calculate at Gross or Net and clicks Adjust Affected VAT Defaults, nothinghappens because Calculate at Gross or Net does not affect any other VAT Defaults. If you then overrideVendor Registration Country and clicks Adjust Affected VAT Defaults again, the system adjusts all VATDefaults except Vendor Registration Country. This time Calculate at Gross or Net was overridden, whichmeans that you will probably have to override this VAT default again to undo the adjustment.

In another example, if you override Vendor Registration Country and click Adjust Affected VAT Defaults, thesystem adjusts all VAT Defaults except Vendor Registration Country and Vendor Registration ID. Then youoverride Place of Supply Driver and clicks Adjust Affected VAT Defaults again. The system adjusts all VATDefaults except Service Type, Place of Supply Driver, Vendor Registration Country and Vendor Registration ID.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Creating SJEs, page 147


PeopleSoft Global Options and Reports 8.8 PeopleBook, “Working with Value Added Taxes(VAT),” Understanding Value Added Taxes (VAT)

Setting Up VAT Options and Defaults for GeneralLedger Processing

To set up VAT options and defaults, use the following components:

• VAT Defaults (VAT_DEFAULT_SEARCH)

• General Ledger Definition (BUS_UNIT_TBL_GL)

• Journal Source (SOURCE)

• Account (GL_ACCOUNT)

Use the ACCOUNT_CF component interface to load data into the tables for the Account component.


• Set up VAT defaults for the General Ledger VAT Drivers.

• Set up General Ledger Business Unit VAT Default Options.

• Set up VAT Default Options for Journal Source .

• Set up Account VAT Defaults for an Account.



Pages Used to Set Up VAT Options and Defaultsfor General Ledger


VAT Defaults Setup VAT_DEFAULTS_DTL • Set Up Financials/SupplyChain, CommonDefinitions, VAT andIntrastat, Value AddedTax, VAT Defaults, VATDefaults Sub-Search, VATDefaults Setup

• Click the VAT Defaultlink on either the GeneralLedger Definition - VATDefaults page, the JournalSource - Definition page,or the Define ChartField -Account page.

Accesses the VAT defaultsto the journal line for theGeneral Ledger businessunits, source, and account.The default fields areavailable on the VATDefaults Setup page for thebusiness unit, the source, andthe account based on thepage where you select theVAT Default link.

General Ledger Definition -VAT Defaults

BUS_UNIT_TBL_GL5 Set up Financials/SupplyChain, Business UnitRelated, General Ledger,General Ledger Definition,VAT Defaults

Defines VAT options thatdefault to the journal linefrom your General Ledgerbusiness units and accessthe VAT Default link todefine additional centralVAT defaults.

Note. This page onlyappears if the business unit isassociated with a VAT entity.

Journal Source - Definition SOURCE1 Set Up Financials/SupplyChain, Common Definitions,Journals, Source, Definition

Specify whether the sourceis for Goods or Services andaccess the VAT Default linkto define additional centralVAT defaults.

Account GL_ACCOUNT Set up Financials/SupplyChain, Common Definitions,Design ChartFields, DefineValues, ChartField Values,Account

Specify whether the accountis for Goods or Services andaccess the VAT Default linkto define additional centralVAT defaults.

Setting Up VAT Defaults for the General Ledger VAT DriversAccess the VAT Defaults Setup page:

Note. The default values on this page are dependent on the VAT Driver you select. Thisexample uses the VAT Driver: BUS_UNIT_TBL_GL.



VAT Defaults Setup page (1 of 2)

VAT Defaults Setup page (2 of 2)

VAT Default Click to access the VAT Defaults Setup page.

The VAT Defaults Setup page is a common page used to set up VATdefaulting for all PeopleSoft applications processing VAT transactions. Onthis page you can define PeopleSoft General Ledger defaults as applicablefor each PeopleSoft defined General Ledger VAT driver.

The General Ledger VAT drivers are:



• Account ChartField

• Journal Source

• GL Business Unit

• VAT Entity Registration

• VAT Country

Note. If you select the VAT Defaults link on the General Ledger BusinessUnit Definition - VAT Defaults page, the Journal Source — Definition page,or the Account page, you will access the VAT Defaults Setup page for theselected driver. All VAT defaults are set up on these central VAT pages.

Note. The VAT Defaults Setup pages are described in detail in thePeopleSoft 8.8 Global Optionsand Reports PeopleBook,“Working with Value Added Taxes (VAT).”


Setting Up General Ledger Business Unit VAT Default OptionsAccess the General Ledger Definition - VAT Defaults page.

General Ledger Business Unit Definition - VAT Defaults page

VAT Reporting Entity Create a VAT Entity for the levels in your organization that requirereporting. You can associate more than one business unit with a VATEntity; however, you can only associate one VAT Entity with a specificbusiness unit. To associate a General Ledger business unit to a VAT Entity,Navigate to Setup Financials/Supply Chain, Common Definitions, VATand Intrastat, Value Added Tax, VAT Entity, Identification.

SeePeopleSoft Global Options and Reports 8.8 PeopleBook, “Workingwith Value Added Taxes (VAT),” Setting Up VAT Entities.

Physical Nature Specify the default nature of transactions for the business unit as either aGoodor Service. The default can be overridden at the source and account level.

Prorate Non-RecoverableVAT

Select to post the Non-Recoverable VAT to the same ChartFields(including account, alternate account, and other ChartFields) that are



specified on the associated expense journal line rather than to a separateVAT account. Selection of this option defaults to the GL JournalEntry - VAT page, VAT Control group box.

Allocate Non-RecoverableVAT

If non-recoverable VAT is not prorated (that is the Prorate Non_RecoverableVAT option is not selected), non-recoverable VAT amounts are postedto a separate VAT account and alternate account. Select this option toallow the chartfield to which non-recoverable VAT will be posted to bedetermined by your Chartfield Inheritance Options. For each chartfield,you may specify that the value always be inherited from the associatedexpense journal line, that the value only be inherited when the VAT isbeing posted to the same General Ledger business unit, that the value beobtained from the set of business unit default ChartFields, or that the VATbe posted to a specific VAT chartfield. Selection of this option defaultsto the GL Journal Entry - VAT page VAT Control group box.

VAT Default link Click this link to access the general ledger business unit driver’s VATDefaults page and define additional defaults for the business unit.

SeePeopleSoft Global Options and Reports 8.8 PeopleBook, “Workingwith Value Added Taxes (VAT),” Establishing VAT Defaults.

Note. Although the VAT amount may be zero, or the VAT may be 100% non-recoverable, the systemgenerates a 0 (zero) Recoverable VAT entry. This is necessary because the VAT Transaction Loader alwaysuses the Recoverable VAT entry as the basis for generating the VAT_TXN_TBL entries.

See Also

Chapter 3, “Defining Your Operational Structure,” Defining PeopleSoft General Ledger BusinessUnits, page27

Setting Up VAT Default Options for Journal SourceAccess the Journal Source - Definition page.



Journal Source - Definition page

Physical Nature Specify the default nature of transactions for the journal source as either aGoodor Service. The default can be overridden at the account level.

Note. Indicate thedefaultoption used most often for VAT transactionsthat use this source. For options that you use less frequently, overridethese defaults at the Account Definition level.

VAT Default link Click this link to access the source central VAT Defaults Setuppage for the Journal Source VAT Driver.

Note. The VAT Defaults Setup page displays for the specific JournalSource you select such as ONL, AP, and AR.


See Also



Setting Up VAT Defaults for an AccountAccess the ChartField Values - Account page.



Account page

VAT Account Flag SeePeopleSoft 8.8 Application Fundamentals for Financial ManagementSolutions, Enterprise Service Automation, and Supply Chain ManagementPeopleBook, “Defining and Using ChartFields,” Adding Account Values.

Physical Nature Specify the default nature of transactions for the account as either aGoodor Service. The defaults override source and business unit defaults.

VAT Default Click this link to access the account central VAT Defaults Setup pageand define the VAT defaults for an account.


See Also


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining and Using ChartFields,” Adding Account Values

Creating and Processing Journals with VATThis section discusses how to:

• Enter VAT in the General Ledger journal header.

• Enter VAT in the General Ledger journal lines.



• Update VAT data in the General Ledger journal VAT lines.

You normally enter VAT data as part of a PeopleSoft subsystem transaction. VAT is calculated withinthe transaction, the transaction is edited, the VAT Transaction Loader is run, and the transaction isposted. Use PeopleSoft General Ledger to enter adjustments, corrections, or miscellaneous transactionsthat either include VAT or affect only the VAT portion of a transaction.

See Also


Pages Used to Create and Process Journals with VAT



JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries, Header, click theLines tab.

Includes business unit, anyVAT accounts that areentered or generated, andthe ability to override thecurrency, rate, and basisamount. VAT default datafrom the business unit,journal source, and VATaccount(s) impact defaultson the GL Journal Entry —VAT page.

GL Journal Entry - VAT JOURNAL_ENTRY_VAT Click the VAT link on thejournal line.

Overrides VAT defaultinformation generated fromthe business unit, source, andaccount that are entered onthe header and lines pages ifnecessary.

Entering VAT in the General Ledger Journal LinesAccess the Create Journal Entries − Lines page.

To enter VAT Lines data:

1. You can override the business Unit on the journal line; however, the selected businessunit must have VAT functionality.

2. If you enter a transaction with its associated Cartridges for a VAT-applicable account, the systemgenerates the VAT journal lines. Or, you can enter a journal line directly against a VAT accountas an adjustment to a VAT transaction along with the appropriate ChartFields.

3. You can override the default Currency and Rate Type. The Exchange Rate displays based on these two values.

4. Enter the Amount.

5. Click the VAT link to access the GL Journal Entry - VAT page.



Note. The Lines page operates in deferred processing mode. Most fields are not updated or validateduntil you save the page or refresh it by clicking a button, link, or tab. This delayed processing hasvarious implications for the field values on the page. For example, if a field contains a default value,any value you enter before the system updates the page overrides the default. Also, the system updatesquantity balances or totals only when you save or click the Calculate Amounts button.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Entering Journal Line Information, page 119

Updating VAT Data in the General Ledger Journal VAT LinesAccess the GL Journal Entry − VAT page.

GL Journal Entry VAT page 1 of 2



GL Journal Entry VAT page 2 of 2

Expanding and Collapsing Sections

To manage your VAT data more efficiently, you can expand and collapse sections tothis VAT page easier to for the user manage.

Expand All Sections Click the expand button to scroll to and access every section onthe page. You can also expand one or more sections by clickingthe arrow next to the section’s name.

Collapse All Sections Click to collapse all sections displaying only the header information.If you expand one or more sections, you can click the arrow next tothe section’s name to collapse the section.

Updating VAT Values

You can modify any of the accessible fields on this page. These are the VAT default values thatyou defined in the VAT Default Setup page for the Account CharfField , Journal Source , GLBusiness Unit), VAT Entity Registration, or VAT Country VAT Driver.


Note. If you modify any of the VAT values on this page, be sure and use the optionsin the Adjust/Reset VAT Defaults group box.

VAT Defaults

Adjusting or resetting VAT defaults will only affect the fields within this VAT Defaults group box:



Adjust/Reset VAT Defaults • Adjust Affected VAT Defaults

If you changed any fields on this page, these changes may impact VATdefaults on this page. For accuracy and consistency, click this buttonif you want the system to adjust the VAT defaults that are affected byyour changes. All changes you have made to VAT Defaults on this pagethat affect other VAT Defaults on this page will be retained.

Click the “i” button to list the fields that will be adjusted.

Note. PeopleSoft recommends that you always click the Adjust AffectedVAT Defaults button after changing any defaults on the VAT page.

• Levels

The levels affected when you click the Reset All VAT Defaults buttonmay be different depending the application you are working with andthe type of VAT page you are working on.

Note. Reset completely redetermines the VAT defaults. This doesnot necessarily mean they will be reset to their original values. Forexample, the user may not have changed any VAT default values, butif a VAT driver field was changed, pressing Reset will redetermineall defaults based on the new driver value.

- All lower levels

Do not select this option for PeopleSoft General Ledger VATbecause it only has one level.

- This and all lower levels

Do not select this option for PeopleSoft General Ledger VATbecause it only has one level.

- This level only

Select this field value to reset all VAT defaults on this VAT page.

• Reset All VAT Defaults

Click this button if you want the system to reset the VAT defaults based theLevels value you selected. All changes you made to VAT defaults will be lost

Importing VAT Data from Third-Party SystemsIn this section we discuss how to import VAT journals using GL_JRNL_IMP.



Page Used to Import VAT from Third-Party Systems


External Flat Files - FlatFile Journal Import

LOAD_JRNL_PNL General Ledger, Journals,Import Journals, ExternalFlat Files, Flat File JournalImport

Imports journal datacontained in a flat file andinserts into PeopleSoftjournal tables.

See Also

Chapter 6, “ Integrating and Transferring Information Among Applications ,” ImportingJournals from Flat Files Using GL_JRNL_IMP , page 76

Importing VAT Journals Using GL_JRNL_IMPAccess the Flat File Journal Import page.

GL_JRNL_IMP Use this utility to insert rows into the PS_JRNL_HEADER, PS_JRNL_LN,PS_JRNL_VAT, PS_OPEN_ITEM_GL, and PS_JRNL_CF_BAL_TBL tablesfrom data contained in a flat file. A commit is performed after all data inthe file loads successfully. If the commit process fails, the entire loadprocess is rolled back. You can run multiple instances of this ApplicationEngine process with smaller flat files in a logical unit of work.

The flat file rows should be grouped in hierarchical order with the headerfirst, followed by its associated journal lines and control lines.

The system uses two system sources, EXT and EXV, to import data. SystemSource EXT enables the system to recognize that VAT Applicable/VATAccount selection is associated with an account and proceeds to calculate VATand generates the additional accounting lines to be posted to the VAT accounts.

System source EXV prevents the system from processing the journal forVAT so you can load all VAT information from a flat file. Therefore,use EXV to import VAT information and populate the JRNL_VAT tablewith transactions exactly as they are in the flat file, and use EXT to loadjournals to populate any missing values with default values and VAT lineswhen necessary. Once the system populates JRNL_VAT, the importedVAT information is picked up by the VAT Transaction Loader.

See Also



CHAPTER 14

Calculating Average Balances

This chapter provides an overview of average balances, or as it is often called, averagedaily balance (ADB) calculation and discusses how to:

• Prepare your system for average daily balancing.

• Process average daily balances.

• Produce average daily balance reports.

Understanding Average Balance CalculationThis section discusses:

• Summary of Capabilities.

• Ledgers used by ADB.

• Average balance calculations.

• How ADB determines calculation method.

• Incremental calculations.

• Ad hoc calculations.

• Adjustments in ADB.

• Period 998 adjustments in ADB.

• Management versus regulatory ADB reporting.

PrerequisitesPerform activities to set up ADB for the detail ledger to be used to maintain the standardbalances and daily balances used to calculate the averages.

Before you can use the ADB feature, you must set up your business units and ledgers for ADB processing.


Calculating Average Balances Chapter 14

Setup: Where What

Business Units Access Setup Financials/SupplyChain, Business Unit Related, GeneralLedger, General Ledger Business UnitDefintion

Set up the business units for whichyou want to calculate average dailybalances.

Select the ADB IncrementalCalculation Method link on theGeneral Ledger Business UnitDefinition page and select thedefinitions that you run regularly(using the incremental calculationmethod) for this business unit.)

Detail Ledgers Access General Ledger, Ledgers,Detail Ledger

Set up these ADB Detail Ledgers:

• LOCALMTD

• LOCALQTD

• LOCALYTD

Ledger Groups Access General Ledger, Ledgers,Ledger Group

Set up these ADB Ledger Groups:

• LOCALMTD

• LOCALQTD

• LOCALYTD

Associate the ledger group with one ofthe ADB Templates.

ADB Templates Access General Ledger, Ledgers,Templates.

Select each of the PeopleSoft ADBTarget Ledger Templates:

• STNDADBMTD

• STNDADBQTD

• STNDADBYTD

• STNDADBDTD

• Verify that the ADB records assetup.

• Add the applicable ADB detailledger to each of the templates tostore the average balances.

The ADB process determines whereto store the calculated averages usingthe table defined in Record (Table)Name field on this template. Create aunique template for each unique tablename depending on where you wantto store the averages. For example, ifyou want to store all the averages toone table, you only need one template.To set up the template, select theADB Reporting Ledger as the DefaultLedger Type and click the button toselect the default table names. Youcan accept the default table or chooseanother ADB target ledger table.


Chapter 14 Calculating Average Balances

Setup: Where What

Access Set Up Financials/SupplyChain, Business Unit Related,General Ledger, Ledgers For A Unit −Definition page.

• Select Report Average Balancesand select an ADB Calendar for theACTUALS (RECORDING) detailledger.

• Indicate whether you want toMaintain Regulatory Balances.

• Select the Filter Posted Activitycheck box.

• Click the Filter link to access theInclude Account Types Posted toADB Ledger secondary page andselect the ADB Account Types. Youcan add more than one account typeand click OK. )

Note. Filters enable you to specifywhich account types you want topost to the ADB ledger, for example,Asset and Liability

Access Set Up Financials/SupplyChain, Business Unit Related,General Ledger, Ledgers For A Unit −Definition page. Add the ADB ledgergroup to the business unit. This iswhere the ADB calculation processlooks to determine what ledger groupand ledger to use to calculate theaverages.

• Attach the ADB Ledger Groups thatyou created to the business unit.

This is where the ADB calculationprocess looks to determine whatledger group and ledger to use tocalculate the averages.

• Select a detail calendar in theCalendar ID field. The calendar canbe a daily or monthly calendar. Forexample:

- LOCALMTD calendar could bemonthly (D1).

- LOCALTD Calendar could bedaily (D2).

The calendar you select determineshow the average balances are stored.If you select a monthly calendar, forexample, the current period reflectstoday’s averages (or the day ADB wasprocessed in the current month) andthe prior period reflects the month-endaverage balances.

Note. Do not select the ReportAverage Balances or any other ADBrelated fields for these ADB Targetdetail ledgers that you attach to abusiness unit in Ledgers For a Unit.



Common Elements Used in This Chapter

Target ADB Ledger(targetaverage daily balance ledger)

Stores the average balances. The Detail Ledger must be a different ledger.

Incremental Method Method of calculating ADB that uses prior period calculated averagesand daily balances to calculate the requested periods’ averages. Moreefficient processing than Ad Hoc Method.

Ad Hoc Method Method of calculating ADB that uses the daily ledger balancesto calculate the requested periods’ averages. It uses more systemresources than Incremental Method.

ADB Average Daily Balance

Period Type Defines the time period for the ADB calculation (Month to date, Year to date).

Average Daily Balance SetupAfter you complete the ADB prerequisites described previously, you must perform the followingactivities before you can process average balances for a business unit. You must:

• Define the interrelationship of ledgers and ChartFields used in ADB on the ADBDefinition page which includes:

- The ledgers and amount fields to be used in the ADB calculations and the interrelationship betweenthe ADB Ledger and target ADB ledger’s amount fields (Definition page).

- The ChartField and value that is used to store the ADB rounding adjustment (Rounding Adjustment page)

- The association between the ADB and target ADB ledgers’ ChartFields (ChartFields page).

• Select the ADB Incremental Calculation Method link on the General Ledger Business Unit Definition page andselect the definitions that you run regularly (using the incremental calculation method) for this business unit.

• Access the ADB Process Request page to run the ADB calculation process (GL_ADB_CALCX).

Summary of CapabilitiesThe Calculating Average Balances feature enables you to report your organization’s financial positionusing average, rather than period-end, balances. You can do the following:

• Select which ChartField values are included in average balances.

• Select the time periods for Average Daily Balance (ADB) calculations from month-to-date,quarter-to-date, and year-to-date options—or define your own time periods.

• Report prior day and current average balances.

• Summarize ADB Target ledgers for summary ledgers.

Ledgers Used by ADBThere are two ledgers involved in ADB processing: ADB Ledger and Target ADB Ledger.



• The Source ADB Ledger (also known as the ADB Ledger) stores the daily ledger activity thatis used by the ADB process to calculate the average daily balances.

• The Target ADB ledger stores the calculated averages from the ADB process.

You can have as many target ADB ledgers as you need.

This design has several advantages.

• Flexibility to maintain the average balances in different ledger tables:

- Partition your averages to different target ledger tables, such as period type (MTD—month-to-date,YTD—year-to-date, and QTD—quarter-to-date), which can improve processing performance.

- You can also maintain all the averages in a single table.

• Flexibility to define a Calendar ID to maintain the calculated average daily balance history:

- To maintain month-end balances only use the monthly calendar ID, which representsthe current day’s averages.

- To maintain daily balances use the daily calendar ID.

See Also

Chapter 14, “Calculating Average Balances,” Prerequisites, page 255

Average Balance CalculationsChoose either the incremental or the ad hoc calculation method.

ADB uses either the incremental method or the ad hoc method to calculate average balances.This table summarizes the differences between the two methods:

Incremental Ad hoc

Uses prior period stored aggregate balances and dailybalances to calculate the requested periods’ averages.

Uses the daily ledger balances to calculate the requestedperiods’ averages.

More efficient processing. Uses more system resources.

How ADB Determines Calculation MethodBy default, the ADB Calculation process (GL_ADB_CALCX) uses the Ad Hocmethod to calculate average balances.

In order to use the incremental calculation, you must define the ADB definitions and periodtype on the General Ledger Definition − Incremental Calculation Method page; period typesrelate to the ADB Definition on that page as follows:



ADB Definition Period Type

Actuals MTD Averages MTD (month to date)

Actuals QTD Averages QTD (quarter to date)

Actuals YTD Averages YTD (year to date)

In the sections that follow, there are examples of how these period types are used in calculations.

Incremental CalculationsIncremental calculations are the most efficient way to calculate average balances. Each time thesystem processes ADB calculations, it extracts only the daily balances that have been posted sincethe last time it ran the ADB Calculation process. The process uses the prior period averagesas the starting point to calculate the current period’s average.

The ADB incremental calculation method determines average balance by dividing the aggregateamount by the number of days within the requested period type:

Average Balance equals the Aggregate amount divided by the number of accumulateddays in the requested period type

Aggregate Amount The aggregate amount equals today’sending balanceplus thepreviousaggregate amount(the aggregate amount for the previous day of this period).

If it is the first day of a period, theaggregateamount is equal to theending balanceand theaverage balance.

Ending Balance Amount The ending balance amount equals today’s daily balance plus thepreviousending balance(the ending balance of the previous day of this period).

If it is the first day of a period, theending balanceis the same asthe aggregateamount and theaverage balance.

The following two tables illustrate incremental calculation by showing how February 1 is calculatedusing two different time periods (period types), year-to-date and month-to-date.

This table shows how the system calculates February 1 for a YTD (year to date) period.

Incremental Calculation for YTD

The following table shows how the system performs incremental year to data calculations.



Year to Date Example: February 1 is the 32nd day of the period.

Incremental Calculation for MTD

The following table shows how the system calculates February 1 for a MTD (month-to-date) period.



Month to Date Example: February 1 is the first day of the second period.

Ad Hoc CalculationsAd hoc calculations require more system resources. Each time the system processes ADB calculations,it extracts data forall the days within the period type from the ADB ledger. Therefore, youusually want the system to use the incremental calculation method for regularly scheduled averages(MTD, YTD and QTD). Otherwise, you can use the ad hoc method.

The ad hoccalculation for average balance is the same as the incremental calculation:

Average Balance = Aggregate / number of days with in the requested period type

The difference is that the Ad Hoc method does not use prior period balances. Instead, it requiresall the daily balances needed to calculate the requested period type. (The incremental processrequires only the daily balances from the previous period.)

This table shows how the system calculates average daily balances for a date-to-date period type (DTD),starting January 5th through the request date of February 1. The ADB ledger uses a monthly calendar.

Calculation Using a DTD Period Type

This table shows incremental Day to Day calculations.



Incremental day to day calculations

In this case, even though February 1 is in the next period, the system still uses the previousday’s ending balance and aggregate amount in the calculation.

In the sections that follow, there are examples of how these period types are used in calculations.

Adjustments in ADBADB adjustments are any transactions for a specific period that have been posted to the ADB Ledgerafter ADB calculations have been run which includes that period in the average balances.

For example, suppose averages balances are calculated at 8:30 Monday morning as of period1. Additional transactions are posted to the ADB Ledger at 9:00 that same morning. Thesenew transactions are considered ADB adjustments.

If the ADB process is using the incremental calculation method, the process automatically adjustsprior period balances before it calculates the requested period averages, because the incrementalcalculation method uses prior period balances to calculate the current period averages (thus theadjustments must first be applied to those prior balances).

If the ADB process isnot using the incremental calculation method, then the processdoesnot have ending balances.

The ADB process adjusts all average balances starting from the minimum accounting period of the ADBadjustments, as long as that accounting period is within the same fiscal year as that of the requested period.



Keep in mind the distinction between ADB adjustments and adjusting journals (which are posted to specialadjustment periods). They are very different and are processed by ADB differently.

Period 998 Adjustments in ADBAdjustment journals are those journals that have been marked as adjustments in the journal headerrecord. PeopleSoft General Ledger posts these journals to special adjustment periods, which aredefined on the Calendar Periods page. They arenot posted to the period of the journal date. Thisprevents period-to-period reporting from being distorted by the adjustments.

ADB calculations supportall adjustment periods.

For the most part, you will probablynot want to include adjustment periods in ADB calculations,with the possible exception of year-to-date daily averages.

If you do choose to include period 998 adjustments, you have two points in the period that you caninclude the period 998 adjustments. You can include them at the beginning of the period, in which caseperiod 998 is considered the first day of the period or you can include them at the end of the period, inwhich case period 998 is considered the last day of the period. For ADB definitions using the incrementalcalculation method, the process calculates the 998 adjustments as of the last day of the period regardlessof the option selected. However, you can choose to run the ADB process using the Ad hoc method onthe ADB request if you want to include the adjustments as of the first day of the period. The impactof period 998 adjustments on average balances is illustrated in the table that follows.

The example assumes that Account 100000 has a 0 beginning balance. During the course of themonth only two transactions were posted, one on 12/1 and one on 12/31.

Account Journal Date Period Day withinPeriod

TransactionAmount

100000 12/01/96 12 1 100

100000 12/31/96 12 31 150

100000 12/31/96 998 300 < − adjustingentry

The following table shows the results of not including period 998, including it at the beginningof the period or including it at the end of the period.

Period 998 Option ADB Calculation Result

No Adjustment Period ADB = ( [100 * 31] + [ 250 * 1] ) / 31

[Aggregate of the 12/1 amount] plus[aggregate of 12/31 amount] dividedby the number of days.

108



Period 998 Option ADB Calculation Result

As First Day of Report Period ADB = ( [400 * 31] + [550 * 1] ) / 31 408

As Last Day of Report Period ADB = ( [100 * 31] + [550 * 1]) / 31 118

See Also


Management versus Regulatory ADB ReportingWhen you enter journals, you identify an ADB date. The ADB date is the date that the system usesto determine in which accounting period the transaction is posted to the ADB Ledger. Usually theADB date and the journal date are the same, but in some cases they might differ.

PeopleSoft General Ledger can maintain separate daily balances for the period, one that reflects thejournal date and one that reflects the ADB date. You specify this requirement by selecting MaintainRegulatory Balances on the Ledgers For A Unit − Definition page.

When you select maintaining regulatory balances, for every journal that has an ADB date thatdiffers from the journal date, the system creates two additional entries: an entry for the periodbased on journal date and a reversal for the period based on ADB date.

The following tables illustrate how ADB maintains regulatory balances. The first table identifies ajournal with ADB date different from the Journal date on lines 3 and 4:

Jrnl Line BU Ledger Acct Jrnl Date ADB Date Amt

1 US001 Corporate 100000 01/01/98 01/01/98 100.00

2 US001 Corporate 100000 01/02/98 01/02/98 200.00

3 US001 Corporate 100000 01/03/98 01/01/98 50.00

4 US001 Corporate 100000 01/04/98 01/02/98 50.00

The second table illustrates the daily balance stored only for the ADB date. This table shows thetransactions as they are posted to the ADB Ledger based on ADB date only:



BU Ledger Account Acct Period Posted TranAmount

US001 Corporate 100000 1 150.00

US001 Corporate 100000 2 250.00

And the last table illustrates the daily balances stored based on both dates.

BU Ledger Acct Acct Per Per Seq* PostedTrans Amt

Comments

US001 Corporate 100000 1 0 150.00 Balanceposted fromADB date

US001 Corporate 100000 2 0 250.00 Balanceposted fromADB date

US001 Corporate 100000 1 1 -50.00 Reversalfor balancesposted fromADB date

US001 Corporate 100000 2 1 -50.00 Reversalfor balancesposted fromADB date

US001 Corporate 100000 3 1 50.00 Balanceposted fromjournal date

US001 Corporate 100000 4 1 50.00 Balanceposted fromjournal date

The Period Seq (period sequence) field distinguishes the balance types: 0—balances posted from ADBdate; 1−balances posted from journal date and reversals for balances posted from the ADB date.

See Also




Preparing Your System for Average Daily BalancingTo prepare your system for average daily balancing, use the ADB Definition component (ADB_DEFN).

This section provides an overview and discusses how to:

• Identify the ledgers.

• Identify rounding adjustments.

• Identify the ChartFields.

Pages Used to Set Up Average Balances


ADB Definition - Definition ADB_DEFN General Ledger, AverageDaily Balance, ADBDefinition

Identify the ledgers and theiramount fields to be used inthe definition.

ADB Definition - RoundingAdjustment

ADB_ADJ General Ledger, AverageDaily Balance, ADBDefinition, RoundingAdjustment

Identify the ChartFields inwhich the ADB roundingadjustment is stored. Whenaverages are calculated frombalanced ledger data, thecalculated averages may notbe in balance because ofrounding. However, dailybalances must be balanced.The ADB process createsrounding adjustments inorder to bring the calculatedaverages back into balance.

ADB Definition -ChartFields

ADB_CF General Ledger, AverageDaily Balance, ADBDefinition, ChartFields

Identify the ChartFieldvalues from the ADBledger that you includein the average balancecalculations.

Identifying the LedgersAccess the ADB (average daily balance) Definition - Definition page.



ADB Definition page

ADB Type(average dailybalance type)

Management Balances- Calculates ADB from the daily balancesposted from theADB date.

Regulatory Balances- Calculates the ADB from the daily balancesposted from the journal date.

Ledger Enter the name of the detail ledger associated with the ADB ledger.

Target Ledger Select the ledger that stores average balances. (You must havecreated this ledger using the Detail Ledger, Detail Ledger Group,and Ledgers For A Unit pages.

Batch Work Record Enter the name of the temporary table used during the ADB calculation process.

Adjustment Period Option Select whether the ADB calculation includes the Period 998balances. Values are:

As First Day of Report Period- The system treats the period 998 balancesas the first day of the report period’s transaction (based on period type)and includes the balances in the ADB calculation.

As Last Day of Report Period- The system treats the Period 998 balancesas the last day of the report period’s transaction (based on period type)and includes the balances in the ADB calculation.

No Adjustment Period- The ADB calculation doesnot includeperiod 998 balances.

Map Amount Fields This section connects the Amount field of the ADB ledger to the target ADBledger’s amount, ending balance, and aggregate amount fields. Refresh bringsup default amount fields for the posted transaction amount, posted totalamount, and posted base amount fields. You can map up to three amount fields.



Ledger ADB Amount(ledger average dailybalance amount)

The column in the ADB Amount Record table where the systemstores daily balances for this ledger.

When you click the Refresh button, all the amount fields for the ADBledger are displayed. Click the Remove button to delete the amountfields you do not want to create average balances for.

Target ADB Amount(target average daily balanceamount)

The column in the target ledger’s table where the systemstores the average balance.

Target Ending Balance The column in the target ledger’s table where the systemstores the ending balance.

Target Aggregate Amount The column in the target ledger’s table where the systemstores the aggregate amount.

See Also

Chapter 14, “Calculating Average Balances,” Prerequisites, page 255

Chapter 14, “Calculating Average Balances,” Understanding Processing of ADB, page 272

Chapter 14, “Calculating Average Balances,” Period 998 Adjustments in ADB, page 264

Identifying Rounding AdjustmentsAccess the ADB (average daily balance) Definition - Rounding Adjustment page.



ADB Rounding Adjustment page

Balanced ADB(balancedaverage daily balance)

Select Balanced ADB to have the system automatically verify whetherselected ledger amounts balance, and to adjust average balance calculationsfor rounding discrepancies. The system also records related adjustmentsto the value of the rounding adjustment entry ChartField you specifybelow. To record average balances without automatic roundingadjustments, clear the Balanced ADB check box.

ChartField Locate the ChartField to use for automatic rounding adjustments.

ChartField Value Specify a value for the ChartField to use for automatic rounding adjustments.

Identifying the ChartFieldsAccess the ADB (average daily balance) Definition - ChartFields page.



ADB ChartFields page

Click the Refresh ChartFields button to retrieve all the ChartFieldsdefined for the ADB ledger (the source ledger). Click View Allto display all the ChartFields.

The ADB calculation process creates an average balance for every ChartFieldcombination listed. Click the Remove button (next to the Detail LedgerChartField field) to delete unwanted ChartFields.

For example, if your ledger has Account, Department, Product,Program, and Project ChartFields, but you only want to have averagebalances for Account/Department/ Product ChartField combinations,delete the Program and Project ChartFields.

ADB Chartfields (averagedaily balance ChartFields)

Used to associate the ADB ledger ChartField with the targetADB ledger ChartField.

Detail Ledger ChartField Enter the ChartField of the target ADB ledger associated with theChartField of the ADB ledger.

How Specified You can summarize the Chartfield values. Use this area to specify how theChartfield values are to be summarized for use in the ADB process.

All Detail Values Include all detail values of the selected ChartField.

Selected Detail Values Summarizes the detail ChartField values you select in the Value field inSpecify Values/Range of Values/Tree Node group box.

Range of Values Summarizes the range of values you select in the Value and To Value fieldsin Specify Values/Range of Values/Tree Node group box.

Detail of Selected Parents Activates the Tree and Level fields in which you can select a tree name and levelname (for trees with levels). Summarizes the values rolled up by the parentnode you select the Specify Values/Range of Values/Tree Node group box.



Selected Tree Nodes Activates the Tree and Level fields in which you can select atree name and level name (for trees with levels). Summarizes thevalues rolled up by the tree node you select in Value in the SpecifyValues/Range of Values/Tree Node group box.

Children at a Level Activates the Tree and Level fields in which you can select a tree nameand level name (for trees with levels). Summarizes every node at thespecified level that is a child of the parent node you select in the SpecifyValues/Range of Values/Tree Node group box.

All Nodes at Selected Levels Activates the Tree and Level fields in which you can select a tree name andlevel name (for trees with levels). Summarizes every node at the specified level.

Tree Enter a Tree name if you are using trees to select your ChartFieldvalues for ADB processing.

Level Enter a Level if you are using trees to select your ChartField values forADB processing and the tree you selected uses levels.

Value Enter the tree node or ChartField value to use for ADB processing.

To Value If you selected Range of Values in the How Specified group box,enter the to value of the range here.

Processing Average Daily BalancesThis section provides an overview and discusses how to request the average daily balance process.

Understanding Processing of ADBOnce you establish the basis for average balance calculations, then initiate the background process thatcalculates the balances and updates the target ledger. If you want to run average balances for a ledgerthat has already been archived, you need to restore the ledger and then run the ADB process.

ADB processing includes the following activities:

• Post Journal (GLPPPOST)

Journal Post posts the daily balances into a holding table.

• Post Daily Balances (GL_ADB_POST)

ADB Post posts the daily balances from the holding table into the ADB Ledger (thesourceledger containing the daily balances).

The ADB Post process also posts ADB adjustments to the adjustment holding tables. (ADB adjustments aredaily balances for a period that was posted after the ADB calculation process was run for that period.)


ADB Calculation calculates average balances using transactions from the ADB Ledger and the adjustmentholding tables, and places the results (average balances) in the ADB target ledger.



ADB Calculation creates an ADB Log entry. The ADB log is used by the ADB process to determine whenthe average balances (for a given definition, period type, and requested period) were calculated.

Note. Instead of running Post Journal (GLPPPOST) and Post Daily Balances (GL_ADB_POST)separately, you can run the Journal and ADB Post multiprocess job (GLADBPST) to post thejournals and update the ADB ledger with the daily balances.

See Also

Chapter 14, “Calculating Average Balances,” Adjustments in ADB, page 263


Chapter 20, “Archiving Ledgers and Journals,” page 439

Page Used to Process Average Daily Balances


ADB Process Request ADB_REQ General Ledger, AverageDaily Balance, ADBProcess, ADB ProcessRequest

Identify the businessunit, ADB definition andperiod type you want toprocess. Use also to specifywhether or not you want torecalculate existing averagedaily balances.

Requesting the Average Daily Balance ProcessAccess the ADB Process Request page.

ADB (average daily balance) Enter the ADB definition. In combination with the Period Type field,this determines which calculation method the system uses.

Request Type Select one of the following Request Type options:

Calc End of Per(Calculate for period end date): Calculate only one period’saverage daily balance. The average balance is for the period end date.

Calc Each Per(Calculate for each period): Generate multiple periods’average daily balances, one for each day of the reporting period.

Period Type Period Type defines the time period for the ADB calculationand, in combination with the ADB field, it determines whichcalculation method the system uses.

Select the Period Type option for average balance calculations. Values are:

DTD (date to date)—Calculates average balances from the specified BeginDate to the date specified in Req Date Option (request date option).Begin Date appears when you select this option.

MTD (month to date)—Calculates average balances from the first dayof the month, which is the beginning date of the accounting period inwhich the run request date falls, to the date specified in Req Date Option.



To use this option, the detail ledger for the business unit must be tiedto a detail calendar that uses monthly periods.

QTD (quarter to date): Calculates average balances from the first day of thequarter, which is the beginning date of the first accounting period in thequarter in which the run request date falls, to the run request date (Req DateOption). To use this option, the detail ledger for the business unit must betied to a detail calendar that uses monthly periods 1 through 12.

Reg Date(regular date): Calculates average balances for a date range that youenter in Begin Date and End Date, which appear when you select this option.

Reg Per(regular period): Calculates average balances from thebeginning date of the From Period to the ending date of the To Periodfor the specified Fiscal Year. The From Period, To Period, and FiscalYear appear when you select this option.

YTD (year to date): Calculates average balances from the first day ofthe year, which is the beginning date of accounting period 1, to therun request date specified in Req Date Option.

Fiscal Year If you selectedReg Per(regular period) in Period Type, enterthe fiscal year for the period here.

From Per (from period) If you selectedReg Perin Period Type, enter the beginning period here.

To Per (to period) If you selectedReg Perin Period Type, enter the ending period here.

Begin Date If you selectedReg Datein Period Type, enter the beginningdate for the date range.

If you selectedDTD in Period Type, enter the beginning date forthe average balances calculation.

End Date If you selectedReg Datein Period Type, enter the ending date for the date range.

Request Date Option Specify the date option for the ADB process. Values are:

Process Date:Uses the process date of the business unit as therequest date for the ADB process.

SYSDATE:Uses the system date as the request date for the ADB process.

As-Of Date: Uses the date you specify in the As of Date field, whichappears when you select this option.

If As Of Datewas selected in the Req Date Option, the As Of Datefield and Update As of Date button appear above the Process Requestgroup box. Use the Update As of Date button to globally update the asof date for requests that use the as-of date option.

If you only want to update the as of date for one of the ledgers listed,use the As of Date in the process request row.

Tree Date Optn (treedate option)

Select the effective date of the tree used to select the ChartFieldsvalues to be processed. Values are:



Use EndDt(use period end date): Sets the effective date to theend of the accounting period.

Use OverDt(use override date): Activates a field in which you canenter a date other than the period end.

Use Override Date If you selectedUse OverDtin the Tree Date Option field, enter a date otherthan the period end date to be used as the effective date for the tree.

Adhoc Select this option if you want to recalculate average balancesusing the ad hoc method.

Description Identify this run of average balance calculations with a short description,such as the date and type of processing.

See Also

Chapter 14, “Calculating Average Balances,” How ADB Determines Calculation Method, page 259

PeopleSoft PeopleTools PeopleBooks: Process Scheduler, "Understanding PeopleSoft Process Scheduler"

Producing Average Daily Balance ReportsThis section discusses how to:

• Run the ADB definition report.

• Run the ADB calculation report.

Understanding ADB Report ProcessingTo run a report select it from a menu and enter the necessary parameters. Once you enter the report parameters,you use Process Scheduler to actually run the report. Process Scheduler manages the processes, tracks thestatus, and generates the report behind the scenes while you continue to work on something else.

For those of you who want to modify our standard reports, create your own reports or reformatreport output, PeopleSoft offers a variety of reporting tools.

Note. Summary ledgers support summarization of ADB (average daily balance) Target ledgers.However, summarizing daily ledgers is not supported.



Pages Used to Produce Average Daily Balance Reports


ADB Definition Report RUN_GLS5500 General Ledger, AverageDaily Balance, ADBDefinition Report

Specify the run parametersfor the ADB DefinitionReport.

ADB Calculation Report RUN_GLC5501 General Ledger, AverageDaily Balance, ADBCalculation Report, ADBProcesses

Specify the run parametersfor the ADB ProcessesReport.

Running the ADB Definition ReportAccess the ADB Definition page.

Data reported:

ADB Amount Record(average daily balanceamount record)

The column in the ADB Amount Record table where the systemstores daily balances for this ledger.

Work Table Record The name of the work table ledger.

ADB Amount Field(average daily balanceamount field)

The name of the ADB Amount Field and whether it has anadjustment period or not.

Balanced ADB (balancedaverage daily balance)

Indicates with aY or N whether the system automatically verifiesif selected ledger amounts balance, and to adjust average balancecalculations for rounding discrepancies.

Running the ADB Calculation ReportAccess the ADB Calculation Report page and complete the Report Request Parameters.


CHAPTER 15

Processing Multiple Currencies in PeopleSoftGeneral Ledger

The following provides an overview of multiple currency processing and discusses how to:

• Prepare to revalue account balances.

• Define revaluation steps.

• Prepare to translate ledger balances.

• Set up translation rules.

• Define translation steps.

• Prepare for the translate within ledger process.

• Combine steps into a multicurrency group.

• Initiate multicurrency processing.

• Put it all together.

• Produce revaluation and translation reports.

Overview of Multiple Currencies in General LedgerThe uniquely flexible PeopleSoft structure enables you to manage financial information inmultiple currencies—you can use a ChartField to designate different currency codes within aledger or, as required, store each currency in a different ledger.

PeopleSoft also provides specific input, processing, and reporting features that satisfy the mostdemanding requirements of multinational financial management. We support the European commoncurrency (euro) as well as currency conversions, remeasurement, revaluation, and translation. Wealso provide a complete audit trail of all multicurrency processing.

PeopleSoft also includes position accounting, which enables you to identify and track the risks associatedwith holding financial assets in currencies other than your base currency.

See Also

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Processing Multiple Currencies,”Setting Up Position Accounting


Processing Multiple Currencies in PeopleSoft General Ledger Chapter 15

Preparing to Revalue Account BalancesPeriodically, you may need to revalue the base currency of the balance sheet accounts that you maintain inforeign currencies to reflect changes in value due to fluctuations in exchange rates. The PeopleSoft GeneralLedger Revaluation (FSPCCURR)adjusts the base currency valueof the account balances by creating adjustingentries for the accounts being revalued. It creates corresponding entries for any gain or loss that results fromthe revaluation. Revaluation typically takes place at the end of each accounting period prior to translation.

For example, suppose that a company whose base currency is USD (U.S. dollars) madethe following cash deposits in CHF (Swiss francs):

Transaction Date Swiss Francs Exchange Rate U.S. Dollars

January 10, 2003 100 0.45 45

January 15, 2003 100 0.50 50

January 20, 2003 100 0.55 55

January 31, 2003 Balance 300 150

At month end, revaluation takes place at the CHF to USD exchange rate of 0.55. The account is revaluedat 165 USD (300 * 0.55 = 165). The following journal entry recognizes the increase in value with a debitof 15 USD to the asset account and a corresponding credit to the revaluation gain account.

Description Debit Credit

Cash in Bank 15 USD

Revaluation Gain 15 USD

Note. General Ledger revalues ledger balances for all foreign currencies.

When you want the results of revaluation to go into accounts that are different from the source accounts, usethe Target ChartField Entry page, on which you can indicate target unrealized gain and loss accounts.

Setting Up Revaluation

In PeopleSoft General Ledger, the following processing takes place when you revalue accounts:

• Revaluation gains and losses are calculated for accounts maintained in foreign currencies.

• Balances of affected accounts are adjusted to the new value.

The system generates an adjusting entry to the base currency balance plus a correspondingentry to the revaluation gain/loss account.


Chapter 15 Processing Multiple Currencies in PeopleSoft General Ledger

You can choose to:

• Create journal entries to reverse the revaluation results in the following period.

• Create journal entries to provide an audit trail of revaluations automatically.

• Report revaluation gains and losses using PS/nVision.

Defining Revaluation StepsTo define revaluation steps, use the Revaluation Step component (REVAL_STEP).


• Specify a ledger and TimeSpan for revaluation.

• Specify source ChartFields for revaluation.

• Specify output and journal options for revaluation.

• Specify gain and loss ChartFields for revaluation.



Pages Used to Define Revaluation Steps


Ledger and TimeSpan REVAL_STEP_LED_TM General Ledger, ProcessMulti-Currency, Define andProcess, Revaluation Step,Ledger and TimeSpan

Use to define a ledger,TimeSpan and rate type forrevaluation.

Source Chartfields REVAL_STEP_CF General Ledger, ProcessMulti-Currency, Define andProcess, Revaluation Step,Source ChartFields

Use to identify accounts torevalue.

Output and Journal OptionsCURR_STEP_OUT_JR General Ledger, ProcessMulti-Currency, Define andProcess, Revaluation Step,Output and Journal Options

Use to specify outputoptions, journal information,and revaluation reversaloptions.

Also, use the TranslationStep − Output and JournalOptions version of thispage to determine whetherPeopleSoft General Ledgerautomatically poststranslated amounts to theledger or generates journalentries for subsequentposting

Gain and Loss Chartfields CURR_STEP_GN_LS General Ledger, ProcessMulti-Currency, Define andProcess, Revaluation Step,Gain and Loss ChartFields

Use to identify therevaluation gain and lossaccounts or to specify thespecific accounts whereyou record translation gainor loss.

Specifying a Ledger and TimeSpan for RevaluationAccess the Ledger and TimeSpan page.



Revaluation Step - Ledger and TimeSpan page

From Ledger GroupandLedger

Specify the from ledger group and specific ledger in which you wantto perform the revaluation. Youcannotspecify a translation ledger forrevaluation. If you don not specify a ledger, revaluation revalues the amountsof all the ledgers in the ledger group. In order to revalue a ledger group withKLS (keep ledgers in sync) selected you must leave the Ledger field blank.

TimeSpan PeopleSoft General Ledger generates journal entries whose amountsrepresent the period of time indicated by the TimeSpan for the revaluationbeing processed. The TimeSpan normally used for balance sheet accountsis BAL (year-to-date). With this TimeSpan, the system totals the accountbalances in periods0 throughn for balance sheet accounts.

Rate Type Enter the exchange rate type for the process.

Specifying Source ChartFields for RevaluationAccess the Source ChartFields page.



Revaluation Step - Source Chartfields page

ChartField Select the ChartField (for example,Accountor Alternate Account) for whichvalues are to be revalued using the TimeSpan and rate type specified.

How Specified List your accounts individually by clicking the Selected Detail Valuescheck box or, more likely, click the Selected Tree Nodes check box.The latter option activates the Tree Information fields for you to specifya tree from which to select nodes. Using trees establishes rollups forthe account values, so you can select particular types of accountsaccording to the structure of your business unit.

Tree Use trees to establish rollups for account values.

Level This field l is optional. If the tree has levels, you can limit promptingin this field to selected levels.

ChartField Values/TreeNodes

Select particular types of accounts according to the structure of your businessunit. We recommend that you use trees whenever possible to reducefuture maintenance should your ChartField values change.

Specifying Output and Journal Options for RevaluationAccess the Output and Journal Options page.



Revaluation Step - Output and Journal Options page

Journal ID Mask Identifies the revaluation journal naming convention that you specify.PeopleSoft General Ledger identifies journals by a 10 character alphanumericidentifier. The system automatically names journals starting with themask value that you specify here. For example, if you entered a mask ofREVAL1, the system begins sequentially numbering journals it creates withREVAL10001. Alternatively, if you do not use the journal ID mask, the systemassigns the next 10 character available journal ID number automatically.

If you use a journal ID mask, reserve a unique mask value to ensurethat no other process creates the same Journal ID.

Description Describes this revaluation step.

Source Identifies the source of the journals. You can select any validsource on the Source table.

Document Type If you enabled PeopleSoft Document Sequencing in your system, select apredefined document type for your revaluation journals. Document sequencingrequires that you have a document type for all of the journal entries you create.

Create Journal Entries Creates journal entries with a header status ofV = Valid that can beposted automatically as part of revaluation processing or through thenormal posting methods. Select the Post Journal(s) check box along withthis option to automatically post the journals created.

Edit Journal(s) Because values being processed are from previously edited data inexisting ledger tables, journal entries are created with a valid status.However, you can submits journal entries created by revaluation tothe journal edit process to be validated for such things as changes tocombination edits or inactivated ChartFields. You can then review thejournals using journal inquiry after you edit them.



Note. To restrict further activity for inactive accounts that have balances,you bypass journal edit and post translation journals for these accounts.Remove the check mark from the Edit Journals check box to bypassjournal edit. The multicurrency process handles the multibook processingfeatures within journal edit for these journals.

Budget Check Journal(s) Submits journal entries to the budget processor for the control budget.

Post Journal(s) Posts the journals to the target ledger as part of revaluation processing. Whenyou process multiple revaluation steps together, where each step dependson the results of the previous step, you must select this check box for allbut the last step to provide updated ledger balances for each subsequentstep. In the last step, posting the journals is optional.

The journals created by multicurrency processing are not intendedor designed to be viewed using the journal entry pages beforerunning journal edit or journal post.

Note. When you run revaluation on secondary ledgers in a multibook ledger group, the revaluationversion of this page produces a journal with a journal header and journal lines for the secondary ledgersonly. This is done to optimize performance. If you attempt to view these journals using the JournalEntry pages, this type of journal may seem or appear corrupt because there are no primary ledger linesfor the ledger group. If you want to view the primary ledger lines from the Journal Entry pages, therecommended procedure is to run the Journal Edit process on all multicurrency journals. The journalediting process creates the missing primary ledger lines needed to view the complete journal.

SeePeopleSoft Global Options and Reports 8.8 PeopleBook, “Processing MultipleCurrencies,” Setting Up MultiCurrency Processing.

Adjustment Period

Target to AdjustmentPeriod

Click to specify an adjustment period as the accounting period for therevaluation journals and enter a period in the Target Adjusting Period field.

An adjustment period revaluation journal can only be reversed to anadjustment period. If you want to reverse the journal, click the Reversal linkand click the Adjustment Period check box to enter an adjustment period in theSpecify field on the MultiCurrency Process Journal Reversal page.

Reversal

Reversal Click the link to access the option. To facilitate period based reporting,the system generates a reversal for the period that follows the revaluationprocess period. The net amount that results on the target ledgerrepresents the current period YTD (year-to-date) amount less thereversal amount generated by the prior period process run. (The reversaljournal date is calculated using the as-of-date of the process request,the reversal option, and business unit calendar.)

Select a Reversal Code:



Do Not Generate Reversal Select for no automatic reversal of this entry.

Beginning of Next Period Creates a reversing entry dated the first business day of the nextaccounting period. It uses the business calendar that you assigned tothe business unit on the General Ledger Definition − Definition pageto determine the first business day. This is the default.

End of Next Period Creates a reversing entry dated the last business day of the next accountingperiod. The business calendar that you assigned to the business unit on theGeneral Ledger Definition − Definition page determines the last business day.

Next Day Creates a reversing entry dated the next business day. This option uses thebusiness calendar that you assigned to the business unit on the General LedgerDefinition − Definition page to determine the next business day.

Adjustment Period Select and enter an adjustment period in the Specify field only forrevaluation journals for adjustment periods.

On Date Specified By User Click and specify a date in that you want in the Reversal Datefield.

Reverse even if cross years Reverse even if reversal occurs in the next year.

Target ChartFields

ChartField Select the ChartFields to be included in the revaluation journal entries.The ChartFields defined here relate to the ChartFields you specifiedon the Specifying Gain and Loss ChartFields for the Revaluationpage. If you are balancing by ChartFields, include all balancingChartFields as your target ChartFields.

Retain Value (retainChartField value)

You can either select this check box or enter a ChartField valuein the Chartfield Value column.

If you select this check box, the ChartField values are carried over from thesource transaction entries to the system generated position accounts.

For the ledger defined on the Ledger and TimeSpan page and for a balancingChartField as defined in the ledger group, if Retain Value is selected forthe gain and loss ChartFields, it must also be selected here for the TargetChartField. If Retain Value is not checked for gain and loss ChartFields,then it is clear for the Target ChartField. All three fields must have thesame ChartField value if retain value is not checked.

ChartField Value If you did not select the Retain Value check box, use this field to specifythe ChartField value that is to be used for the system generated targetaccount. If you enter a ChartField value here, the system ignores theChartField value on the source transaction entry.

When a ChartField value is not included in target ChartFields,it is blank for the target journals.

Extra gain or loss entries can be created from multiple runs of revaluation, if thegain ChartField value is different from the corresponding loss ChartField value.



Specifying Gain and Loss ChartFields for RevaluationAccess the Gain and Loss ChartFields page.

Revaluation Step - Gain and Loss Chartfields page

General ledger posts the offsetting entries that correspond to the adjusting entries created during revaluation tothe accounts specified below—credits to the gain ChartFields, debits to the loss ChartFields.

Gain ChartKeys Enter the ChartField and either click the Retain Value check box orenter a value in the ChartField Value field.

ChartField Here you indicate the ChartFields to be included in the revaluationgain and or loss journal entries. If you are balancing by ChartFields,include all balancing ChartFields (do not include business unit andcurrency) as your target ChartFields.

Retain Value (retainChartField value)

You can either check this box or enter a ChartField value inthe Chartfield Value field.

If you check the box, the ChartField values are carried over from the sourcetransaction entries to the system-generated position accounts.

Click Retain Value for a ChartField for both gain and loss, or for neither. So,for the same ChartField, either click both check boxes, or clear both.

For the ledger defined on the Ledger and TimeSpan page, for a balancingChartField as defined in the ledger group; if Retain Value is clicked for thegain and loss ChartFields, it must also be clicked for the Target ChartField.If Retain Value check box is clear for gain and loss ChartFields, then itis clear for the Target ChartField. All three fields must have the sameChartField value if Retain Value is clear (not selected.)



Extra gain or loss entries may be created from multiple runs of revaluation ifa ChartField is set to retain value in gain or loss but not in target. If someChartFields are not included as target ChartFields, they will be blank.

ChartField Value If you did not click the Retain Value check box, use this field to specifythe ChartField value that are to be used for the system generated targetaccount. If you enter a ChartField value here, the system ignores theChartField value on the source transaction entry.

When a ChartField value is not included in target ChartFields, itwill be blank for the target journals.

Loss ChartKeys For the Loss ChartKeys field, enter the Loss ChartField and either check theRetain Value check box or enter a ChartField value. The field definitions forthe loss ChartFields are the same as for gain ChartFields. If a ChartFieldretains value for gains, it must retain value for loss, and conversely.

Note. When you balance by ChartFields, if a balancing ChartField is designated as a gain or lossChartField then the balancing ChartField overrides the value specified on this page.

Preparing to Translate Ledger BalancesPeopleSoft General Ledger translates posted balances into different currencies according to the rules youdefine, and calculates gains or losses due to restatement. You can execute translation at any time because it isa background process. General ledger can perform regular translation on any type of ledger.

If you perform multiple translations for each business unit—such as a remeasurement followedby translation—PeopleSoft General Ledger enables you to define a separate set of processingrules for each translation. It considers each translation as atranslation step.You can processas many translation steps as you require at one time.

Note. Although remeasurementis considered a separate process to precede translation under FASB52, it is defined in PeopleSoft General Ledger as a translation step with different exchange rates.To perform a remeasurement, set up a translation step as described in this section to translateyour base currency balances to functional currency balances. You can also use the multibookfeature to maintain a secondary ledger in your functional currency.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Understanding Ledgers



Setting Up Translation RulesBecause different accounts are translated according to different exchange rate rules, you can use theTranslation Rule pages to define which accounts are processed with which conversion rate types.This information defines your approach to translating types of accounts. For example, you cantranslate your asset and liability accounts at the current rate, but use historical rates to translate equityaccounts. You refer to these rules when you define your translation steps.

To set up translation rules, use the Translation Rule component (TRANS_RULE).


• Define TimeSpans and rates for a translation rule.

• Define ChartFields for a translation rule.

Pages Used to Set Up Translation Rules


TimeSpan and Rate TRANS_RULE_TIME_RT General Ledger, ProcessMulti-Currency, Define andProcess, Translation Rules,TimeSpan and Rate

Use to define Time Spansand Rates for a TranslationRule.

Chartfields TRANS_RULE_CF General Ledger, ProcessMulti-Currency, Define andProcess, Translation Rules,Chartfields

Use to indicate theChartFields for theTranslation Rule.

Defining TimeSpans and Rates for a Translation RuleAccess the TimeSpan and Rate page.

Translation Rule - TimeSpan and Rate page



TimeSpan PeopleSoft General Ledger generates journal entries for amounts that representthe period of time indicated by the TimeSpan for the translation rules beingprocessed. The TimeSpan normally used isITD (inception-to-date profit andloss accounts) orBAL (balance sheet accounts). With these TimeSpans,the system sums the account balances in periods 1 throughn for P&Laccounts and periods 0 throughn for balance sheet accounts.

Rate Type Select the applicable exchange rate type.

Defining ChartFields for a Translation RuleAccess the Chartfields page.

Translation Rule - Chartfields page

ChartField Select the ChartField (Account) to be translated using the TimeSpan and ratetype specified. For example, assets and liabilities are typically translatedas balances (BAL) at the current exchange rate (CRRNT) while retainedearnings are translated at a historical exchange rate (HSTRE).

How Specified For example, list your asset accounts individually by clicking theSelectedDetail Values check box or, more likely, click the Selected Tree Nodescheck box. The latter option activates the Tree Information fields foryou to specify a tree from which to select nodes.

Tree Enter each tree node—while entering level is optional. If the tree haslevels, you can limit prompting in this field to selected levels. Using treesestablishes rollups for the account values, so you can select particulartypes of accounts according to the structure of your business unit. Werecommend that you use trees whenever possible to reduce futuremaintenance should your ChartField values change.



Defining Translation StepsUse the Translation Step pages to define how a specific translation is to be processed.

To define translation steps, use the Translation Step component (TRANS_STEP).


• Specify ledgers for translation.

• Specify rules for translation.

• Specify output and journal options for translation.

• Specify gain and loss ChartFields for translation.

Pages Used to Define Translation Steps


Ledger TRANS_STEP_LED General Ledger, ProcessMulti-Currency, Define andProcess, Translation Steps,Ledger

Use to specify the sourceand target ledger group andledgers for a translation step.

Rule TRANS_STEP_RULE General Ledger, ProcessMulti-Currency, Defineand Process, TranslationSteps, Rule

Use to specify whichtranslation rules to use inthis step.

Output and Journal OptionsCURR_STEP_OUT_JR General Ledger, ProcessMulti-Currency, Define andProcess, Translation Steps,Output and Journal Options

Use the Specifying Outputand Journal Optionsfor Revaluation pageto determine whetherPeopleSoft General Ledgerautomatically post translatedamounts to the ledger orgenerates journal entries forsubsequent posting.

Gain and Loss Chartfields CURR_STEP_GN_LS General Ledger, ProcessMulti-Currency, Define andProcess, Translation Steps,Gain and Loss Chartfields

Use to specify the specificaccounts where you recordtranslation gain or loss.

Specifying Ledgers for TranslationAccess the Ledger page.



Translation Step − Ledger page

From Ledger Group Specify the ledger group to be translated.

From Ledger Required for translation. You can translate any type of ledger in a group,including secondary, primary, and translation ledgers.

Target Ledger Group Select the target ledger group that is to receive the results. Translationonly creates journals to a ledger group that is defined as a translationledger in the Ledger Group Type field on the Detail Ledger Group page.Translation creates balances for the primary ledger of the target ledgergroup. Other adjustment journals are allowed to this ledger.

From Currency Type Select one of the following values :

• L (ledger base currency) - The system uses the base currencyof the from ledger.

• S (specify) - Specify a value in the From Currency field.

Translation translates to the base currency of the target ledger, and populatesboth the foreign amount and the monetary amount on the journal, which inturn populates the POSTED_TOTAL_AMT and POSTED_BASE_AMTon the translation ledger. These two fields always are the same on theledger. In other words, the foreign currency and the base currency willalways be the same for the journals posting to this ledger.

From Currency If you selected S (specify) in the From Currency Type field, select thecurrency code in the from currency drop down menu.

Specifying Rules for TranslationAccess the Rule page.



Translation Step - Rule page

Translation Rule Select the translation rules while keeping in mind that any translation rules thatyou select here you must have already defined in the Translation Rules table.

Specifying Output and Journal Options for TranslationAccess the Output and Journal Options page.

Translation Step - Output and Journal Options page

Use the section discussing Specifying Output and Journal Options for Revaluation page to completethis page. PeopleSoft General Ledger can generate journal entries for subsequent posting.



See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” Specifying Outputand Journal Options for Translation Within Ledger, page 297

Specifying Gain and Loss ChartFields for TranslationAccess the Gain and Loss ChartFields page.

Translation Step - Gain and Loss Chartfields page

Use the section Specifying Gain and Loss Chartfields for Translation Within Ledger to complete most ofthis page, which determines the specific accounts for which you record translation gain or loss.

However, the following two check boxes appear on the translation step version of this page only:

Check Balance of Step Click this check box to have the system check the balances of your step entriesto ensure that they are balanced. Checking the balance on your translation stepdefinition entries protects the integrity of your target ledger. If you specify yourtarget ledger as a balanced ledger and you leave this option clear, youmustclickthe Generate Adjustment check box so that your target ledger stays balanced.

Generate Adjustment Click this check box to have the system calculate a currency adjustment. If youdo a partial translation, your gain or loss includes an offset required to bringyour step into balance in addition to the actual currency adjustment. If you clearthis check box, the Gain ChartFields and Loss ChartFields are unavailable.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” Specifying Gainand Loss ChartFields for Translation Within Ledger, page 297



Preparing for the Translate Within Ledger ProcessAt the end of the accounting period, you can run a translation process calledTranslate Within Ledgeragainstthe translation ledger to produce the appropriate gain or loss adjustment. This process handles the translationledger in the same manner as does revaluation processing. The Translate Within Ledger process only processestranslation ledgers. (Revaluation processes regular secondary ledgers but not translation ledgers.)

You prepare for this process on the Detail Ledger Group - Definition page by establishinga particular ledger as aTranslation Ledger.

When journal lines are generated online for the secondary ledgers of a multibook ledger group, the basecurrency is calculated differently for currency (“MultiBook" ) translation ledgers than fornormalsecondaryledgers. Normal secondary ledger lines contain a foreign currency and foreign amount equal to the transactioncurrency and transaction amount of the primary ledger. For multibook translation ledgers, lines are generatedwith the foreign currency and foreign amount equal to that of the base currency and base amount of the primaryledger. This results in multibook translation ledgers having at most one foreign currency at any time. Thisforeign currency will always be the base currency of the primary ledger of the ledger group.

The Translation Within Ledger process generates a translation adjustment with the multibook translationledger for specified accounts in order to maintain a real time balance for the accounts. Use the TranslateWithin Ledger Group pages to define the criteria for running this process.

To prepare for the Translate Within Ledger process, use the Translation Within Ledger component (MBXLAT).


• Specify a ledger and TimeSpan for translation within ledger.

• Specify ChartFields for translation within ledger.

• Specify output and journal options for translation within ledger.

• Specify gain and loss ChartFields for translation within ledger.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Linking Ledgers to a Ledger Group



Pages Used for the Translate Within Ledger Process


Ledger and TimeSpan MBXLAT_STEP_LED_TM General Ledger, ProcessMulti-Currency, Defineand Process, TranslationWithin Ledger, Ledger andTimeSpan

Use to define a ledger andTime Span for the TranslateWithin Ledger process.

Chartfields MBXLAT_STEP_CF General Ledger, ProcessMulti-Currency, Define andProcess, Translation WithinLedger, Chartfields

Use to identify the accountsyou want to include inyour step.

Output and Journal OptionsCURR_STEP_OUT_JR General Ledger, ProcessMulti-Currency, Define andProcess, Translation WithinLedger, Output and JournalOptions

Use to determine whetherPeopleSoft General Ledgerautomatically poststranslated amounts to theledger or generates journalentries for subsequentposting.

Gain and Loss Chartfields CURR_STEP_GN_LS General Ledger, ProcessMulti-Currency, Defineand Process, TranslationWithin Ledger, Gain andLoss Chartfields

Use to specify the specificaccounts where you recordtranslation gain or loss.

Specifying a Ledger and TimeSpan for Translation Within LedgerAccess the Ledger and TimeSpan page.

Translation Within Ledger - Ledger and TimeSpan page

Although the Translation Within Ledger - Ledger and TimeSpan page is a different object from theRevaluation − Ledger and TimeSpan page, both pages have all their fields in common.



From Ledger GroupandLedger

Specify the from ledger group and specific ledger in which you want toperform the Translate Within Ledger process. Youmustspecify a translationledger for this process. If you do not specify a ledger, Translate Within Ledgeris run by the system against all the translation ledgers in the ledger group.

TimeSpan PeopleSoft General Ledger generates journal entries for which the amountsrepresent the period of time indicated by the TimeSpan for the step definitionbeing processed. The TimeSpan typically used is BAL (balance sheetaccounts). With this TimeSpan, the system totals the account balancesin periods 0 throughn for balance sheet accounts.

Rate Type Enter the applicable rate type for the process.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” Specifying aLedger and TimeSpan for Translation Within Ledger, page 295

Specifying ChartFields for Translation Within LedgerAccess the Chartfields page.

Translate Within Ledger - Chartfields page

Although this ChartField page is a different object from the Revaluation − Source Chartfields page, both pageshave their fields in common. Please see the Specifying Source ChartFields page for the revaluation topic.

Chartfields Select the accounts to be processed in the Chartfields group box. Forexample, you can list your balance sheet accounts individually as detailvalues or, more typically, you define tree nodes. Using trees establishesrollups for the account values, so you can select particular types of accountsaccording to the structure of your business unit.



Note. If the currency code is specified in the ChartFields, the system processes only the ledgerbalances for that currency code. When a currency code is not part of the ChartFields, thesystem revalues ledger balances for all foreign currencies.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” SpecifyingSource ChartFields for Revaluation, page 281

Specifying Output and Journal Options for TranslationWithin LedgerAccess the Output and Journal Options page.

Translate Within Ledger - Output and Journal Options page

Use the discussion for Specifying Output and Journal Options for Revaluation page to specify output options,journal information, and revaluation reversal options for the Translation Within Ledger process.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” SpecifyingOutput and Journal Options for Revaluation, page 282

Specifying Gain and Loss ChartFields for TranslationWithin LedgerAccess the Gain and Loss Chartfields page.



Translate Within Ledger - Gain and Loss Chartfields page

Use the discussion of the Specifying Gain and Loss Chartfields for Revaluation page to specifyyour Translate Within Ledger gain and loss accounts.

See Also

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” SpecifyingGain and Loss ChartFields for Revaluation , page 286

Combining Steps Into a MultiCurrency GroupOnce you have defined the steps necessary to accomplish your desired revaluation, translation, or TranslateWithin Ledger process , you define a multicurrency group that specifies the processing sequence for these steps.

To combine steps into a multicurrency group, use the Currency Group component (CURR_GROUP).

This section discusses how to combine steps in a multicurrency group.

Page Used to Combine Steps in a MultiCurrency Group


Multi-Currency ProcessGroup

CURR_GROUP General Ledger, ProcessMulti-Currency, Define andProcess, Define ProcessGroup, Multi-CurrencyProcess Group

Use to define amulticurrency Group.

Combining Steps In a MultiCurrency GroupAccess the Multi-Currency Process Group page.



Multi-Currency Process Group page

Sequence The sequence number determines the order in which the system performsthe steps. Since the ledger may be updated with each step, it is importantto perform the steps in the appropriate sequence.

Process Step Enter the revaluation, translation, or Translate Within Ledger Process step.The system displays the description for the process step. After defininga step, you can select it for the multicurrency group sequence. You canalso reuse steps from other multicurrency groups.

Continue Check to indicate that even if this step fails, processing shouldcontinue to the next step.

Initiating MultiCurrency ProcessingThis section discusses how to request multicurrency processing.

Page Used to Initiate MultiCurrency Processing


Multi-Currency ProcessRequest

CURR_REQUEST General Ledger, ProcessMulti-Currency, Define andProcess, Request Process,Multi_Currency ProcessRequest

Once you have specifiedthe MultiCurrency Group,use this page to set up aMultiCurrency processingrequest



Requesting MultiCurrency ProcessingAccess the Multi-Currency Process Request page.

Multi-Currency Process Request page

Group Identify the multicurrency group to be processed with this request, forexample,REVALBALfor Revaluation processing.

When errors occur and processing aborts, you can restart processingat the step that failed by clicking the Start Step check box rather thanprocessing all the steps in a process group. This option becomesavailable only if errors occurred during processing.

Calc Log (calculation log) Click if you want the system to create a log of all the calculationsperformed during processing.

Request Date Option You can select theAs of Date, then specify a date in the As of Date field.You can define steps using relative TimeSpans, such as BAL (currentbalance). A relative time span causes the process you are running to retrieveledger amounts relative to the as of date specified on the MultiCurrencyProcess Request page. The steps processed by this multicurrency processrequest must be effective on or before the as of date.

You can also select theBusiness Unit Process Dateoption, in which case theprocess uses the date option on the business unit general ledger definition.The system retrieves the date, and uses it as the as of date.

As of Date Used to retrieve the following:

• Step definitions

• Tree data

• Currency exchange rates

If a step definition indicates that a journal should be created, then thesystem uses the as of date as the journal date.

Note. The journals created by multicurrency processing were not designed for viewing with the Journal Entrypages. The Journal Edit process should be run against these journals before you attempt to view them.



Putting It All TogetherLet us look at two multicurrency processing scenarios. The first scenario shows how you maintainmultiple books using all multicurrency processes; the second scenario compares the single book translationto the results of maintaining a translation ledger within a multibook environment.


• Use multicurrency processing in a multibook environment.

• Compare multibook translation ledger results to translation in a single book environment.

Note. PeopleSoft General Ledger must be installed and theCreate MultiBook Accounting Entriesin Subsystems check box must be clicked on the Installed Products page for multibook functionalityto be available in subsystems, such as PeopleSoft Accounts Payable.

Using MultiCurrency Processing in a MultiBook EnvironmentIn the following example, we demonstrate MultiCurrency processes in a multibook environment.Suppose your company uses the following ledger structure:

Business Unit: C007 (CHF)

Ledger Group: MULTI-TRAN

Ledgers: • Actuals primary ledger (CHF − inherited from C007)

• Local (EUR)

• Report (USD) translation ledger

Also assume the following currency transactions:

Currency Exchanges Exchange Rate − TransactionDate

Exchange Rate − ReportingDate

MXN to CHF 0.295 0.297

MXN to EUR 0.179 0.175

CHF to USD 0.602 0.605

The results of using revaluation in a multibook environment is explained in the next section.

Using Revaluation in a MultiBook Environment

The following topics discuss various aspects of revaluation processing in a multibook environment.



Beginning Ledger

The following shows the results of revaluation in a multibook environment. Assume that the followingbalances exist in the ledger. Account 2001 is a balance sheet account; 8001 is a P&L (profit and loss) account.The base amount calculations are shown to exhibit the derivation of the base currency balance.

Assumed beginning ledger balances

Month End Revaluation Journal (only revalue balance sheet accounts)

This journal results from running revaluation on the entire ledger group. The revaluation processskips the report ledger because it is specified as a translation ledger. The actuals and localledgers will be revalued. Running journal edit on this ledger carries the adjustments to thebase currency of the actuals ledger down to the report ledger.

Month end revaluation

Ending Ledger

The following table contains the ending ledger amounts after the revaluation.

Ending ledger amounts



Translate Within Ledger Process

After revaluation, you run the Translate Within Ledger process, which generates the translationadjustment. Only the report translation ledger are processed. Continuing with the aboveexample, the report ledger balances are shown below.

Beginning Ledger (Report only)

The following table contains the beginning ledger amounts to appear on the translation ledger for reports only.

Account Foreign Currency Foreign CurrencyBalance

Report (USD)

2001 CHF 29.7 17.881

8001 CHF -29.5 -17.76

Gain/Loss CHF -0.2 -0.121

Month End Translation Journal

The output journal that results from the Translate Within ledger process is shown below. The exampleassumes that the translate within ledger step is defined for balance sheet accounts only, but this neednot be the case. You can, for example, define your translate within ledger step definition to includeprofit and loss, or income statement, accounts to be processed at an average rate.

Month end translation journal

Ending Ledger

The following table showsthe ending ledger amounts after you run the translate process for reports.



Account Foreign Currency Foreign CurrencyBalance

Report (USD)

2001 CHF 29.7 17.9685

8001 CHF -29.5 -17.76

Gain/Loss CHF -0.2 -0.121

Translation Adjustment CHF 0 0.0875

Comparing MultiBook Translation Ledger Results toTranslation in a Single Book EnvironmentMaintaining a translation ledger within a multibook ledger group results in the same ledger balancesas performing a period-end translation on the actuals ledger. To show this, we start with the ledgerbalances for actuals from the example above, after revaluation is run on the ledger group. Weperform a single book translation: actuals (CHF) to ledger group (USD).

Beginning Ledger

The following table shows the ledger balances for actuals ledger after the revaluation is run on the ledger group.

Account Currency Code Transaction Amount Actuals (CHF)

2001 MXN 100 29.7

8001 MXN -100 -29.5

Gain/Loss MXN 0 -0.2

Translation Journal

The following table shows the results of running the translation process on the actuals ledger. The translationis simplified for clarity in this example. The balance sheet accounts are translated at the CRRNT exchangerate and the profit and loss, or income statement, accounts are translated at an average rate.

Assume that the currency exchange rates are as follows:



Conversion and Type Exch Rate on Reporting Date

CHF to USD (CRRNT) 0.605

CHF to USD (AVG) 0.604

Ending Ledger

The following table shows the resulting balances of this single book ledger.

Account Currency Code SB Reports (USD)

2001 USD (29.7 * 0.605) = 17.9685

8001 USD (-29.5 * 0.604) = -17.818

Gain/Loss USD (-0.2 * 0.605) = -0.121

Translation Adjustment USD -0.0295

Compare the resulting balances of this single book translation to the balances in the report ledger of the ledgergroup MULTI-TRAN. The difference of .058 between the translation adjustment and the value for account8001 is due to the fact that the profit and loss, or income statement, account 8001 was translated at the AVGrate, and its offset is included in the translation adjustment. If we had defined an additional translate withinledger step earlier to process this account at the AVG rate type, the balances would be identical.

Producing Revaluation and Translation ReportsBelow are listed standard revaluation and translation reports. To run a report, select it from a menuand enter any necessary parameters. Once you enter the report parameters, use the process schedulerto run the report. The process scheduler manages the processes, tracks the status, and generates thereportbehind the sceneswhile you can continue to work on something else.

For those who want to modify our standard reports, create your own reports, or reformatreport output, we offer a variety of reporting tools.



Pages Used to Produce Revaluation and Translation Reports


Translation Step DefinitionReport

RUN_GLS5000 General Ledger, ProcessMulti-Currency, Reports,Translation Step, TranslationStep Definition Report

Use to specify the runparameters for theTranslation Step DefinitionReport GLS5000 SQR thatlists the details and rules ofeach currency translationstep.

Revaluation Step DefinitionReport

RUN_GLS5001 General Ledger, ProcessMulti-Currency, Reports,Revaluation Step,Revaluation Step DefinitionReport

Use to specify the runparameters for theRevaluation Step Definitionreport GLS5001that listsdetailed information for eachcurrency revaluation step.

Translation CalculationLog Report

RUN_GLS5002 General Ledger, ProcessMulti-Currency, Reports,Translation Calculation Log,Translation CalculationLog Report

Use to specify the runparameters for theTranslation Calculation LogReport GLS5002 SQR thatlists translation calculationdetails by process instanceand translation step.

Revaluation CalculationLog Report

RUN_GLS5003 General Ledger, ProcessMulti-Currency, Reports,Revaluation Calculation Log,Revaluation CalculationLog Report

Use the RevaluationCalculation Log Report pageto specify the run parametersfor the RevaluationCalculation Log ReportGLS5003 SQR that listsrevaluation informationby process instance andrevaluation step.

Translation in LedgerCalculation Log Report

RUN_GLS5004 General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger CalcLog, Translation in LedgerCalculation Log Report

Use to define parameters forthe Translation in LedgerCalculation Log ReportGLS5004 SQR that displaysthe details and rules of eachtranslation step within theledger calculation log. Foreach step, the report showsthe description, ledgerinformation, output andjournal options, and gain andloss ChartKeys.

Translate in Ledger Report RUN_GLS5005 General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger,Translate in Ledger Report

Use to define yourparameters for the TranslateWithin Ledger Step ReportGLS5005 SQR that listtranslation within ledgercalculation details byprocess instance andrevaluation step.



Page Name Object Name Navigation UsageTranslate LedgerReconciliation Report

RUN_GLS1005 General Ledger, ProcessMulti-Currency, Reports,Translation LedgerReconcile, Translate LedgerReconciliation Report

Use to specify the runparameters for the TranslateLedger Reconciliationreport GLS1005 SQR thatreconciles the amounts in thecurrency translation ledgerto the amounts in the primaryledger within a multibookledger group.

You can include AdjustmentPeriods and select AccountType within the comparison.Click the Refresh buttonto select ChartFields forcomparison.

Translation Ledger In-SyncReport

RUN_GLS1006 General Ledger, ProcessMulti-Currency, Reports,Translation Ledger In-Sync,Translation Ledger In-SyncReport

Use to specify the runparameters for theTranslation Ledger In-SyncReport GLS1006 that listsdata violating the requiredledger structure in thecurrency translation ledgerwithin a multi-book ledger.

The structural flaws thisreport shows are as follows:

• Translate Ledger containsnon-Primary base entries

• Translate Ledger containsPOSTED_TRAN_AMTnot equal toPOST_BASE_AMT onmatching entries inPrimary ledger

• Non zero TranslateLedger entries do not havematching entries inPrimary ledger

• Primary ledger entrieswith no matching entriesin Translate ledger

• POSTED_BASE_AMT oftranslate ledger entriesin primary ledger basecurrency do not add up toPOSTED_TOTAL_AMTof entries in translateledger base currency

See Also

PeopleTools PeopleBooks: “PeopleSoft Process Scheduler, Understanding Process Scheduler




CHAPTER 16

Performing Financial Consolidations

This chapter provides an overview of consolidations with related equitization functionality and discusses how to:

• Determine consolidation ChartFields.

• Select an approach to inter/intra company transactions.

• Define consolidation trees.

• Set up elimination units.

• Specify consolidation ledgers.

• Define elimination sets.

• Define subsidiary ownership and minority interest sets.

• Set up consolidation sets.

• Use ChartField value sets.

• Perform consolidation.

• Consolidate across summary ledgers.

• Map dissimilar charts of accounts.

• Use Equitization.

• Define business unit trees and elimination units for equitization.

• Specify ledgers for each business unit in an equitization.

• Define ownership sets for equitization.

• Define equitization rules.

• Define an equitization group and journal options.

• Perform equitization.

• Produce consolidation and equitization reports.

• Use the ledger interface utility.

Understanding ConsolidationsThis section discusses:

• Organizational structure and consolidations.


Performing Financial Consolidations Chapter 16

• Elimination of intercompany transactions.

• Elimination of intercompany investments and calculating minority interest.

• Components of the consolidation process.

Organizational Structure and ConsolidationsOrganizations often have complex structures with multiple operating units and legal entities withvarying degrees of ownership. If your organization is comprised of more than one business unitor operating entity, you can consolidate these organizations when you report on overall operations,presenting financial statements that accurately describe your financial status.

For example, Consolidated Manufacturing is a multinational company that has a controlling interestin a United States business as well as numerous other subsidiaries worldwide. The balance sheet forConsolidated Manufacturing lists its United States investment as an asset and also owns several buildingsused by subsidiaries that record the payment of rent to corporate headquarters through intercompanyaccounts. While these companies are separate legal entities, they represent one unified economic entity.To gain a complete picture of the entire organization, you must combine (consolidate) all the assetsand liabilities of each business unit, with intercompany transactions and minority interest relationshipseliminated through the creation of consolidation elimination journal entries.

You use trees to define the relationships among business units in a consolidation, creating a separateconsolidation tree for each configuration. Included in each consolidation tree are the business units beingconsolidated and theelimination unitsto which eliminating journal entries are directed.

Consolidate Any Combination of Business Units


Chapter 16 Performing Financial Consolidations

Elimination of Intercompany TransactionsWhile there may be situations that require you to report gross consolidations (combiningbusiness unit ledger balances without eliminations), in most cases, you want to eliminateor cancel out the effect of intercompany transactions.

In PeopleSoft General Ledger, you can track intercompany transactions using Due From/To accounts thatare automatically created by the Journal Edit process, which calls the Inter/IntraUnit Processor. These DueFrom/To rows in the ledger are candidates for elimination when you run the Consolidations process. Thefollowing example shows such a transaction when Company B0002 buys software for Company B0001:

Business Unit Account Debit Credit

B0001 651001—SoftwareLicense Expense

5,000

B0001 142000—Due From/ToB2

5,000

B0002 141000—Due From/ToB1

5,000

B0002 200000—AccountsPayable

5,000

When the transactions are exclusively within the organization, you may want to eliminate thewhole transaction when you set up your Consolidations process. In the following example,Company B0001 sold services to Company B0002. The Revenue and Expense accounts needto be eliminated in addition to the Due From/To accounts.

Business Unit Account Debit Credit

B0001 142000—Due From/ToB0002

3,000

B0001 500200—Revenue-Services Sold

3,000

B0002 653000—Expense-Computer Networks

3,000

B0002 141000—Due From/ToB0001

3,000



Using the Affiliate ChartField with a Single Due From/To Account

The Affiliate ChartField is specifically reserved to map transactions between business units whenusing a single intercompany account. Let’s examine intercompany payables and receivablesamong three business units that each use the Affiliate ChartField.

Business Unit Account Affiliate Amount

B0001 140000—Due From/ToAffiliates

B0002 <5,000>


B0003 1,000


B0001 5,000


B0003 <3,000>


B0001 <1,000>


B0002 3,000

Using Different Due From/To Account Values

Another method of tracking activity between business units is to use different ChartField values—typicallydifferent accounts—for intercompany transactions. Instead of using the Affiliate ChartField, you could use thefollowing accounts to identify the same transactions that were shown in the previous exhibit.

Business Unit Account Amount

B0001 142000—Due From/To B0002 <5,000>

B0001 143000—Due From/To B0003 1,000

B0002 141000—Due From/To B0001 5,000

B0002 143000—Due From/To B0003 <3,000>

B0003 141000—Due From/To B0001 <1,000>

B0003 142000—Due From/To B0002 3,000



In both examples, the same accounting information is present, but fewer account numbers are required when theAffiliate ChartField is populated. This also means that you need to define fewerelimination sets.An eliminationset represents a related group of intercompany accounts that record both sides of each transaction between units.

In the case of the following intercompany receivable/payable relationship, you require onlyone elimination set if you use the Affiliate ChartField.

Elimination Set Business Unit Account

One N/A 140000—Due From/To Affiliates

If you do not use the Affiliate ChartField, three elimination sets are required:

Elimination Set Business Unit Account

One B0001

B0002

142000—Due From/To B0002


Two B0001

B0003



Three B0002

B0003



See Also

Chapter 16, “Performing Financial Consolidations,” Defining Elimination Sets, page 322



Elimination of Intercompany Investments andCalculating Minority InterestsIn consolidating the books of a subsidiary with those of the parent company, you credit the parentwith the portion of the subsidiary that it actually owns and exclude what outside investors own. Thevalue of minority interests is reported in terms of the aggregate net assets (equity) rather than in termsof a fractional equity in each of the assets and liabilities of the subsidiary.

To reflect minority interest, PeopleSoft General Ledger generates an adjustments entry that debits the investmentof the parent in the subsidiary account and credits a minority interest account. The adjustment is calculated bymultiplying the percentage of minority interest in the subsidiary by the total equity of the subsidiary.



Effectively, the combined result of the adjustments and eliminations entries is to express the valueof the parent investment in terms of the assets and liabilities of the subsidiary offset by a minorityinterest liability. The equity ownership for each subsidiary in the consolidation is eliminated, withonly the parent company’s equity accounts and minority interest account remaining. Consolidatedcapital stock and retained earnings is equal to the balances of the parent.

In the following example, Company B1 owns 80% of Company B2:

Setup for Minority Interest for 20% of Company B2 (0.2 x 50,000)

*Adjustments are netted with the total investment eliminations.

** Elimination of the total equity of B2 versus the investment in Company B2.

Components of the Consolidation ProcessConsolidations are made up of four elements: Data, Scopes, Rules, and Process.

Data Ledger data is entered and posted through daily journal processing andincludes specifying which ledger to use during Consolidations for eachbusiness unit. Detail Ledgers, as well as Summary Ledgers, can be used as the



basis for consolidation. Ledgers residing outside of the PeopleSoft GeneralLedger database can be loaded into the database for processing.

Scopes Scopes define which business units are included during the consolidationprocess and how consolidation entries are created. Scopes are createdusing consolidation trees and Elimination Units.

Rules Rules determine which ledger entries are identified and eliminatedby defining Elimination and Minority Interest Sets. These are usedin defining the Consolidation Set that specifies the Eliminationand Minority Interest Sets to apply.

Process Based on defined rules and scopes, the Consolidations backgroundprocess generates consolidating journals and calculation log entriesfrom source ledger data. New entries to the Ledger table are used togenerate consolidated reports. The Undo feature allows consolidationreprocessing as many times as necessary.

Common Elements Used in This ChapterView Detail Link that accesses another page for more detailed information.

Ledger Template Ledger Template name is used to prompt correct ChartField names.If a Summary Ledger Template is specified as the Ledger Templatein setting up consolidations, the Ledger edit box is activated toinput the Summary Ledger Name.

Determining Consolidation ChartFieldsYou can base your consolidations on the Business Unit or other ChartField in your system.


• Consolidate on Business Unit.

• Consolidate on a ChartField other than Business Unit.

Consolidating on Business UnitAlthough you can consolidate based on any ChartField, we deliver PeopleSoft General Ledger withconsolidations enabled for the Business Unit. If you use a different ChartField for your consolidations,substitute that ChartField name when you see a reference to Business Unit.



Consolidating on a ChartField Other Than Business UnitFor some organizations, the system is setup to use ChartFields such as Operating Unit or Departmentinstead of Business Unit to function as separate units. Since they are all conducting the same or similarbusiness practice and have the same structure, all the units are under one PeopleSoft Business Unitsetup. Transactions between these operational units are recorded and need to be eliminated for financialreporting of this Business Unit. PeopleSoft General Ledger enables you to setup the consolidation amongthe operational units the same way you would to consolidate among Business Units.

The following steps explain the setup to consolidate on the Operating Unit ChartField:

1. If an affiliate field is to be used to mark inter-operating unit transactions, activate the Operating UnitAffiliate field on the Standard ChartField Configuration page, and associate the Operating Unit field to it.

2. Add Operating Units that function as the Elimination Operating Units to the Operating Unit definition.Assign the attribute ELIM_UNIT equal to Y for these elimination units.

3. Build a consolidation tree that rolls up Operating Unit values including regularand elimination operating units.

4. Set up elimination sets. When you define an elimination set using the Affiliate approach, donot include the ChartField on which you are consolidating.

5. Set up the consolidation set. Specify Operating Unit as the Entity Field and enter the valuefor Business Unit that the operating units are under.

6. Define and process a consolidation request.

7. Create reports that are based on the consolidation tree to show consolidated results.

See Also

Chapter 16, “Performing Financial Consolidations,” Elimination of Intercompany Transactions, page 311

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Summarizing ChartFields Using Trees”

PeopleTools PeopleBooks: "PeopleSoft Application Engine," Using Meta-SQL and PeopleCode

PeopleTools PeopleBooks: “PeopleSoft Tree Manager,” Creating Trees

Selecting an Approach to Inter/Intra Company TransactionsYou can record activity between business units with the use of the Affiliate ChartField or withseparate accounts. The Affiliate ChartField maps transactions between business units whileusing a single inter-company account. Alternatively, you can use different ChartField values,typically different accounts, for inter-company transactions.

If the consolidation is on Business Unit, the consolidation process will assume it is an inter-companyconsolidation, and the Affiliate will be the Affiliate field name.



If the consolidation is on anything other than Business Unit, the process assumes it is an Intracompanyconsolidation within a single Business Unit. For Intracompany elimination when the Affiliate method isused or where Affiliate field is required for querying the ledger data, the associated affiliate field for thatChartField as defined on the Standard ChartField Configuration page will be the field name.

See Also



Chapter 16, “Performing Financial Consolidations,” Elimination of Intercompany Transactions, page 311

Defining Consolidation TreesYou define a consolidation based on relationships among the business units you are consolidating andtheir related elimination units (units to which eliminating journal entries are directed). Each consolidationhierarchy uses a separate consolidation tree. You can consolidate an unlimited number of business unitswithin each tree, and you can define an unlimited number of consolidation trees.


• Define consolidation scopes with trees.

• Add detail values.

Defining Consolidation Scopes With TreesBecause you will likely have several consolidation configurations to accommodate managementand statutory requirements, PeopleSoft General Ledger enables you set up any number ofconsolidation trees. Your consolidated business entities appear as nodes and your business unitsand eliminations units appear as detail values on the tree.

For example, World Wide Consolidation is comprised of 22 business units in Europe, Asia Pacific, andNorth America. For financial reporting requirements, the company created a tree that defines the legalentity relationships among these business units, as well as those located elsewhere.



Consolidation Tree for World Wide Consolidation

The World Wide Consolidation node (WW_Consolidation) represents the final pointof consolidation and the relationship among consolidated entities Europe, ASIA/PAC,NORTH_AMERICA, and an elimination unit ,ELIM1.

Adding Detail ValuesThe detail values in a Consolidations tree always consist of the ChartField values that form the basisfor consolidation and elimination units. Elimination units are stored in the same table as consolidatingChartField values because they share identical attributes; that is to say, if your consolidating ChartFieldvalues are business units, the elimination entities are also defined as business units.

In such a case, the system maintains all your detail values in the general ledger Business Unit table.You can, however, set up consolidations based on any other ChartField.

See Also




Setting Up Elimination UnitsWith Consolidations you can automate intercompany eliminations and more accurately analyzeconsolidated results. When you consolidate business units, the system creates eliminatingjournal entries. Eliminating journals are directed to anelimination unit, a type of business unitthat is designed specifically to support consolidated reporting.

Eliminating journal entries are directed to the elimination unit

The consolidated business entity does not have its own ledger. It is actually a reporting constructmade up of the combined ledger balances of the selected business units and the inter-companyoffset amounts posted to the ledger for the elimination unit.


• Add an Elimination Unit.

• Assign Ledgers to Elimination Units.

Adding an Elimination UnitYou add an elimination unit to the tree in the same way you add any detail ChartField value, by insertinga detail value. Remember that, if you base your consolidations on the Business Unit ChartField,you create and maintain elimination units just as you would business units.

For example, the ELIM5 elimination unit in the consolidated management reporting tree forConsolidated Corporation is defined as an elimination unit. When you press ENTER while on thedetail value (ELIM5), you open to the first General Ledger Definition page.

Acess the General Ledger Definition - Definition page to define each elimination unit. Youcan define these directly or from the consolidation tree.



Eliminations Business Unit Definition page

Assigning Ledgers to Elimination UnitsAssigning a ledger to an elimination unit is done the same way that you handle regular Business Units.The Base Currency of the ledger must be the same currency used for consolidation.

See Also


Chapter 3, “Defining Your Operational Structure,” page 25

Specifying Consolidation LedgersTo specify a consolidation ledger, use the Consolidation Ledger Sets component (LEDGER_SET).

For each business unit involved in Consolidations, you can specify one ledger as the Consolidationledger. The Consolidations process uses this ledger as the source and identifies transactions to beeliminated. Consolidation journals go against this ledger for Elimination Units.

In cases where business units have different base currencies in their primary ledgers and translation ledgersare maintained for reporting on a single currency, you can use Translation ledgers as Consolidation ledgers.Consolidation does not perform any currency translation. Therefore, the currency you specify must havecomplete balances in place resulting from regular journal posting or the Currency Translation process.

You specify a ledger for a business unit on the Ledger Sets page. With a common ConsolidationChart of Accounts, you can also consolidate at a summary level.



Page Used to Define Ledger Sets


Ledger Set LEDGER_SET General Ledger,Consolidate Financial Data,Consolidation, ConsolidationLedger Sets, Ledger Set

Select the combination ofbusiness units and ledgersthat you wish to consolidatefor a specific consolidationconfiguration.

Defining a Ledger SetAccess the Ledger Set page.

Consolidation - Ledger Set page

Automatic Populate Scroll

The Automatic Populate Scroll enables you to select the parameters that will populate the scroll with theledgers you can use. Once you have chosen your parameters, click the Refresh button to populate the page.

Note. The Refresh button only gives you thebest guessof ledger names. You must review the ledgernames populated by the system. If the ledger is not the desired one, you can change it.

Tree Determines the business units that will appear in the scroll. All businessunits in a particular tree will appear in the scroll.

As of Date Use to select a tree if you have multiple trees with the same name.



Currency Populates the Ledger Column with the Ledgers that have thesame base currency defined.

Specify Ledgers to Use

When you click Refresh, the system populates the scroll area with the following:

Business Unit Populates the valid values in the selected tree for the specified ledger template.

Ledger It also displays a ledger associated with each business unit that has thespecified currency as its Base Currency. You can associate a different ledgerwith the business unit by selecting a new one from the drop down list.

You can also enter Business Units and their associated Ledgers individually by adding a row. Thenew business unit does not have to be part of the earlier specified tree.

Note. All business units involved in the consolidation process must have a row defined on the Ledger Set pageso that the system knows which ledger to use for each business unit during the consolidation process.

See Also

Chapter 16, “Performing Financial Consolidations,” Specifying Consolidation Journal Options, page 329

Defining Elimination SetsThe elimination set defines a related group of inter-company accounts. Once eliminated, the balances of thisgroup of accounts should normally net to zero. To maintain a balanced journal entry, the system will postany amounts that remain after the elimination to a user-defined out-of-balance ChartKey. When you run theconsolidation, the system will process each elimination set specified in your consolidation definition.

To define elimination sets, use the Elimination Sets component (ELIMINATION_SET).


• Define an elimination set.

• Enter an elimination set.

• Audit elimination sets.



Pages Used to Work with Elimination Sets


Elimination Sets ELIMINATION_SET1 General Ledger,Consolidate Financial Data,Consolidation, EliminationSets, Elimination Set

Define parameters for theelimination.

Elimination Lines ELIMINATION_SET2 General Ledger,Consolidate Financial Data,Consolidation, EliminationSets, Elimination Lines

Define which accounts youwant to eliminate. Whenyou define these accounts,the level of detail requireddepends on whether youare using the AffiliateChartField.

Audit Elimination Sets RUN_GLS2005 General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets Audit,Audit Elimination Sets

Set up criteria to run theGLS2005 SQR for auditingelimination sets. Determinesif any duplicate lines exist inconsolidation definitions.The system uses the criteriayou enter to generate theAudit Elimination Setsreport.

Defining an Elimination SetAccess the Elimination Set page.

Elimination Set page

Ledger Template Select from the drop-down list box. When a Summary Ledger Template isspecified as the Ledger Template, the Ledger edit box is activated for input



of the Summary Ledger Name. A View Detail link also activates; clickingit will take you to the Summary Ledger Definition page.

Description Identifies the elimination for prompt lists.

Comments Describe exactly what the elimination set does. This is particularly usefulfor documenting each set in a complex consolidation.

Out of Balance Debit and Out of Balance Credit

Field Name Specify special ChartFields for the out-of-balance amounts. Forexample, you can enter a department for both the Debit and CreditField Name in addition to an account Value.

For Summary Ledger Templates, the Field Name prompt lists all theChartFields for the Summary Ledger Template, and the Value promptis based on how the Summary Ledger is defined.

Entering an Elimination SetAccess the Elimination Lines page.

Elimination Lines page

Match Affiliate Value Select the check box if you use the Affiliate approach for elimination. For asummary ledger that does not have an AFFILIATE ChartField, the MatchAffiliate Value check box will be unchecked and grayed.

Values to Eliminate

Field and Value When each intercompany transaction is recorded in a unique account, theBusiness UnitChartField and theAccountor ALTACCTChartField and theirrespective values are required. If you use the Affiliate ChartField and itsrespective value is already a Business Unit, do not enter the Business UnitChartField. The system evaluates Business Unit and Affiliate relationshipswhen you perform the consolidation based on data in the ledger.

In addition to theAccountor ALTACCTChartField, you can specify otherChartFields to further narrow the scope of the transaction being eliminated.This applies regardless of which method you use for tracking intercompany



activity. To prevent duplication, the system does not allow you to enter thesame ChartFields and ChartField values within the same elimination line.

Auditing Elimination SetsAccess the Audit Elimination page.

Audit Elimination Sets page

Report Request Parameters

SetID SetID for the consolidation set.

Consolidation Set Defined for the Consolidation SetID.

As of Date Point of reference for the effective-dated setup information.

Defining Subsidiary Ownership and Minority Interest SetsPeopleSoft General Ledger evaluates minority interest relationships at the time a consolidationis run, based on the data in the minority interest sets and Ownership table. It calculates theadjustment prior to generating elimination entries.

You define the relationship for the subsidiary business unit, the parent company thatowns the majority of that subsidiary, and any other minority owners. You don’t specifyminority owners that exist outside your organization.

If a minority parent exists in the same consolidation tree as a majority parent, PeopleSoft General Ledger makesa second adjustment to reflect the minority parent’s ownership percentage. Since the original adjustment createsa liability for the minority interest, the second adjustment effectively reduces that liability because a minorityparent is included in the consolidated results. This means that you don’t overstate your minority interest liability.

PeopleSoft General Ledger supports any number of minority parents and generates the adjustment entryat the appropriate point in the consolidation according to the consolidation tree level.

To define subsidiary ownership and minority interest sets, use the Subsidiary Ownership component(CONSOL_OWNERSHIP) and the Minority Interest Sets component (MINORITY_INTEREST).


• Define subsidiary ownership.

• Define the minority interest source.



• Define a minority interest target.

Pages Used to Define Subsidiary Ownership andMinority Interest Sets


Subsidiary Ownership CONSOL_OWNERSHIP General Ledger,Consolidate Financial Data,Consolidation, OwnershipSets, Subsidiary Ownership

Define the relationshipsfor the parent company,subsidiary business unit, andany other minority owners.

Minor Int Source (minorityinterest source)

MINOR_INT_SOURCE General Ledger,Consolidate Financial Data,Consolidation, MinorityInterest Sets, Minor IntSource

Identify the subsidiaryequity and parent investmentaccounts.

Minority Int Target(minority interest target)

MINOR_INT_TARGET General Ledger,Consolidate Financial Data,Consolidation, MinorityInterest Sets and select theMinority Int Target page

Specify the minorityaccounts of the majorityparent company.

Defining Subsidiary OwnershipAccess the Subsidiary Ownership page.

Subsidiary Ownership page

Entity Field This field defines the consolidating Business Unit or ChartField. Ifyou change the consolidating ChartField in your trees, you won’thave to redefine all your minority interest sets.

Subsidiary Entity Organizational unit owned by the parent.



Specify Parents

Parent Owner of the subsidiary.

Owner % Amount of the subsidiary owned by the parent. List any minority ownersthat exist within your system by adding rows.

Controlling Entity Indicates which parent is the subsidiary’s majority owner. Use this option toindicate a particular parent business unit for which elimination entries willbe created. The parent company selected as the Controlling Entity holds theminority interest liability. Onlyoneparent entity can be the Controlling Entity.

Note. To prevent duplication, the system does not allow you to enter the same parent business unit values twice.

Equitize Indicates whether Equitization should be run for specified parententities. The system will process this ownership set only when thesubsidiary entity and all the parent entities marked for Equitizationare included in the consolidation tree.

Parents Ownership % Total should be less than or equal to 100%.

Minority Interest % Percentage of Minority shareholder ownership.

Defining the Minority Interest SourceAccess the Minor Int Source (minority Interest source) page.

Minor Int Source (minority interest source) page

Subsidiary Equity Specifies the ChartField Value Set that identifies the subsidiary’sequity accounts.

Parent Investment Specifies the ChartField Value Set that identifies the asset account wherethe subsidiary is carried on the parent company’s books.

Match Affiliate Value Select the check box if you are using a single Investment Account andhave populated the Affiliate ChartField with the subsidiary.



See Also

Chapter 16, “Performing Financial Consolidations,” Using ChartField Value Sets, page 332

Defining a Minority Interest TargetAccess the Minor Int Target (minority interest target) page.

Minor Int Target (minority interest target) page

Minority Interest

Field Name and Value Identifies the parent’s equity or liability account for minority ownership inthe subsidiary. After PeopleSoft General Ledger generates the minorityinterest adjustment, it eliminates the majority parent’s investmentaccount against the subsidiary’s equity accounts.

Out of Balance Debit and Out of Balance Credit

Field Name and Value If the elimination does not balance, the system directs the remaining amountto the appropriate out-of-balance account or ChartFields.

You can specify special ChartFields for the out-of-balance amounts.For example, you can enter a department for both the Debit andCredit ChartFields in addition to an account.

Setting Up Consolidation SetsOnce you define consolidation relationships in your tree and specify intercompany eliminationand minority interest sets, you are ready to define the options and controls that tell PeopleSoftGeneral Ledger how to process the consolidation.

To set up consolidation sets, use the Consolidation Set component (CONSOL_DEFINITION).




• Specify consolidation journal options.

• Specify set options.

Pages Used to Set Up Consolidation Sets


Journal Options CONSOLIDATION1 General Ledger,Consolidation, ConsolidationSet, Journal Options

Specify consolidationprocess options.

Set Options CONSOLIDATION2 General Ledger,Consolidation, ConsolidationSet, Set Options

Specify which eliminationand minority interest sets theconsolidation will include.

Specifying Consolidation Journal OptionsAccess the Journal Options page.

Consolidations Set - Journal Options page

Entity Field ChartField against which the elimination is applied. Most often, theConsolidation unit will be Business Unit.

Business Unit When consolidating on other than BUSINESS_UNIT, PeopleSoft GeneralLedger displays a Business Unit field that enables you to designate thebusiness unit as the high order key in the consolidation.

Ledger Set Specifies a combination of business units and ledgers that act asa centralized location for consolidations.



Elimination Journals

Journal ID Mask Enables you to specify a prefix for naming consolidation journals. A10-character alphanumeric ID identifies journals. The system automaticallyappends the prefix you specify to the journal IDs. For example, if youspecify your Journal ID Mask to beELIMIN, your Elimination JournalIDs might be ELIMIN0001, ELIMIN0002, and so on. Alternatively,the valueNEXTcauses PeopleSoft General Ledger to assign the nextavailable journal ID number automatically.

It is very importantto reserve a unique mask value for Consolidations toensure that no other process will create the same Journal ID.

Source Any valid value from the Sources table entry identifying thesource of the consolidation journals.

Document Type Required for consolidation journals if Document Sequencing isenabled. Document Sequencing requires that you have a DocumentType for all the journal entries you create.

In the following example, Department is the additional ChartField and the eliminationlines contain the following amounts:

ChartField Usedin Eliminations -

Account

ChartField Usedto Group By −

Department

Product Posted Total Amount

1100001 100 XYZ 100.00

2200001 100 XYZ - 80.00

1100001 200 N/A 200.00

2100001 200 N/A -190.00

During Consolidations, the system generates journal entries that represent year-to-date elimination amountsbased on the type of account specified in the elimination set. For P&L accounts, the system totals theYTD amount based on the sum of periods 1 throughn, and for balance sheet accounts periods 0 throughn. To facilitate period-based reporting, PeopleSoft General Ledger generates a reversing journal for thesubsequent period. The resulting net amount on the elimination unit ledger represents the current periodYTD amount less the reversal amount generated by the eliminations for the prior period.

Elimination Reversals

Beginning of Next Periodor End of Next Period

Indicate whether you want to generate Elimination Reversal entries for theBeginning of Next Period or for the End of Next Period. The system will directthe journal entries to the elimination unit specified in the consolidation tree.



Elimination Includes ChartFields

Select the ChartFields you want to include in elimination. The ChartFields defined for a ConsolidationDefinition relate to the ChartFields specified for the elimination set as follows:

• If Elimination Set ChartFields provide more detail than Consolidation Definition ChartFields, the system willsummarize the elimination journal entries at the level of detail defined by the elimination set. For example, ifyou specifyAccountfor your Consolidation Definition, andAccountandProject for your elimination set,the system will include Account and Project detail when it summarizes elimination journal entries.

• If Consolidation Definition ChartFields provide more detail than Elimination Set ChartFields, the systemwill expand the elimination journal entries, summarizing at the level of detail defined by the ConsolidationDefinition. For example, if you specifyAccount, Department, andProductfor your ConsolidationDefinition andAccountandProject for your elimination set, the system will expand the eliminationjournal entries to include Account, Department, and Product detail when it summarizes them.

See Also

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Defining DocumentSequencing,” Defining Document Types

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Defining Journal Source

Specifying Set OptionsAccess the Set Options page.

Set Options page

All Elimination Sets Apply Indicates you want to use all the sets you defined on the EliminationSet page for this consolidation.

Default Minority Int Set(default minority interest set)

Specifies which minority interest set to use for the calculation. Basedon the Subsidiary Ownership setup, Consolidations will include allparents/subsidiary sets provided all entities involved are within theconsolidation scope (meaning the consolidation tree).



Elimination Sets to Process

Elimination Set If you want to use only a portion of the elimination sets, specifythe sets by adding rows in this section.

Minority Interest Sets Override

Ownership Set Associated with Minority Interest Set for consolidation set override purposes.

Minority Interest Set Specifies Minority Interest Set on a certain Ownership Set for consolidationset override purposes. This override can be useful, for example,when you use different equity accounts for certain subsidiaries, andthus define separate minority interest sets.

Using ChartField Value SetsUse ChartField Value Sets to define sets of ChartFields used in consolidation and Equitizationprocesses. You can specify individual values, select values from specified tree levels and nodes,or use ranges of detail values. We recommend that you use trees or ranges whenever possibleto reduce future maintenance if ChartField values change.

You could setup ChartField Value Sets with the same name but different setIDs for different groups of BusinessUnits, if ChartField Values as part of the consolidation rules are different by business units. For example,Parent Investment in the Minority Interest Set definition page is specified as a ChartField Value Set entry. Youcan define two ChartField Value Sets both named ACCT_INVESTMENT, but one under setID SHARE andone under SET01 with each having its own set of accounts specified. The setID for ChartField Value Set will beresolved at run time, based on the TableSet Control for Record Group FS_12, for each Business Unit processed.

You can set up ChartField Value Sets for either detail ledgers or summary ledgers. Specify the summary ledgername, as well as the ledger template. You cannot use Tree to select values for Summary Ledgers.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Defining and Using ChartField Value Sets

Performing ConsolidationThis section discusses how to:

• Initiate consolidation processing.

• View the consolidation process log.

• Use the process monitor.



Pages Used to Perform a Consolidation


Consolidation Request CONSOL_REQUEST General Ledger,Consolidate Financial Data,Consolidation, RequestConsolidation, ConsolidationRequest

Identify consolidationparameters that the systemwill process and how oftenthe GLPOCONS COBOLprocess will run.

Consolidation Process Log CONSOL_PROCESS_INQ General Ledger,Consolidate Financial Data,Review Results Online,Consolidation Process Log

View how and whenconsolidation processesare run. This page alsoshows you the parametersused for undoing previousconsolidation processes.

Consolidation Dashboard CONSOL_PROCESS_MON General Ledger,Consolidate Financial Data,Review Results Online,Consolidation Dashboard

View the consolidationprocess status at the treenode level. You can alsoquery the Calculation Logbased on user-specifiedcriteria.

Initiating Consolidation ProcessingAccess the Consolidation Request page.

Consolidation Request page

Request Parameters

SetID SetID for the consolidation.

Currency Currency used in the consolidation.



Consol Set(consolidationset)

Defined for the Consolidation SetID.

As of Date Serves as a point of reference for determining the year and period toconsolidate for each ledger in the consolidation. If business units usedifferent calendars, the year and period will be evaluated for each.Also used to access the effective-dated setups.

Consolidation Options

Create Journal Entries PeopleSoft General Ledger will create journals that can be edited and/or posted.

Create Calculation Log Creates a calculation log that contains the amounts generated by eachelimination and minority interest set at each tree node. Once the systemcreates the log, you can inquire on the calculation log with the ConsolidationProcess Monitor page, or run the Consolidation Out of Balance (GLS2003)and the Minority Interest Eliminations and Adjustments (GLS2004) SQRs.The Consolidation Out of Balance report examines the elimination sets for theconsolidation as of the date specified, indicates which elimination sets are inbalance and which are not, and shows you the details of any out-of-balancecondition. The Minority Interest Eliminations and Adjustments report detailsthe Majority and Minority Parent eliminations and adjustments based on thehierarchical relationship of business units present in the tree.

Include AdjustmentPeriod(s)

Includes balances from the Adjustment Periods specified in theConsolidation Set when calculating the elimination.

Edit Journal(s) Provides the ability to identify an edit error and process the consolidationagain. The system clears journals from the original process beforeregenerating. Not available if Document Sequencing is enabledat the system or business unit level.

Post Journal(s) Posts journals during consolidation processing. Not available if DocumentSequencing is enabled at the system or business unit level.

Undo Previous Process Clears the effect of any prior elimination. If the elimination journalsare not posted yet, the system deletes them. If they have been posted,PeopleSoft General Ledger removes the amounts from the ledger beforeit deletes the journals. The same applies to elimination reversal entries.The system identifies the previous process by looking at the Key fields ina consolidation process log that stores information about former processes.The Key fields are Consolidation Set, Currency Code, As Of Date, andTree Scope. You can view the process log on the Consolidation ProcessLog page. Select this option if you want to process the whole tree againwhen there is a processing error. You can also run a standalone Undoprocess followed by running the consolidation process.

Undo − Do Not DeleteJournals

The Undo process will not delete unposted journals. If you selectthis option and have journals from the Consolidation process thathave not been posted, you can accidentally post those journals andcause elimination to be double booked.



Note. If the process aborts during an undo, unlock the journals for the process instancebefore rerunning the undo process.

Scope of Consolidation

Tree Specify the applicable Tree for the consolidation.

Scope ChoseProcess the Whole Treeto processes all business units defined inthe consolidation tree or if you chooseProcess at Levelor Process at TreeNodethe Level and Node fields will become available.

Level Processes all business units at and below a particular tree level.Identify the level in the edit box.

Node Processes consolidated business units at and below a particular treenode. Identify the node in the edit box.

Tree Effective Date Option

Use As of Date Uses the date defined for the consolidation.

Use Override Date Select and use any date you define in the Tree Override Date field. Forexample, you may want to consolidate based on a tree that is not yet active inorder to test (using current figures) its effect on future consolidations.

See Also



Viewing the Consolidation Process LogAccess the Consolidation Process Log page.

Consolidation Process Log page

This information is useful if you want to undo a previous consolidation process, but haveforgotten what parameters were used for that process.

The fields on this page are the same as those found on the Run Consolidation page.

See Also

Chapter 16, “Performing Financial Consolidations,” Initiating Consolidation Processing, page 333



Using the Process MonitorAccess the Consolidation Dashboard page.

Consolidation Dashboard page

Tree The Tree Control area displays the consolidation process status of a givenConsolidation Set and Tree, between a certain From Date and To Date.

Calculation Log Criteria

Elim. Set (elimination set) Specifies an elimination set to inquire on consolidation resultsrelated to that elimination set.

Minor Set (minorityinterest set)

Specifies a minority interest set to inquire on consolidation resultsrelated to that minority interest set.

Unit Specifies a business unit to inquire on consolidation results relatedto that business unit. If there is an error involving a Business Unit,you can click the Exception button to the right of the Unit edit box todisplay information in the Message dialog box.

Node The consolidation tree is color-coded with the status of each node. Click thenode on the tree and click the Exception button to the right of the Node edit box.A message about the node status will be displayed in the Message dialog box.

Message Displays messages regarding the consolidation processing status of a businessunit or a node. If there is an error status and the error has been corrected,you can rerun the same process. The consolidation process will resumefrom the point where the error occurred. Status codes include:

• OK - The node is completed and the process was successful.

• Error - An error occurred and needs to be corrected beforethe process can continue.

• Warning- An error occurred (for example, a Journal Edit error),but the process continued.

• Blank - The process has not reached this node yet.



Consolidation Calculation Log

Consol Entity (consolidationentity)

Business Unit or the values of your consolidation entity (forexample, Operating Unit).

Identifier Stores either the Elimination Set or the Minority Interest Set.

Entry Type Identifies one of the following entry types: Elimination, Majority ParentAdjustment, Majority Parent Elimination, or Minority Parent Adjustment.

Consolidating Across Summary LedgersProcessing consolidation on summary ledgers offers the following advantages:

• The process time will be greatly reduced because the volume of summary ledgers usuallyis much smaller than your detail ledgers. This is especially true if you are using existingsummary ledgers that you are already maintaining.

• You can achieve the purpose of consolidating Business Units with dissimilar Chart of Accountsthrough summarizing your detail ledgers using trees.

The following are the main differences when setting up or running the consolidationprocess using summary ledgers:

• Whenever Ledger Template needs to be specified, instead of using a Detail Ledger Template (for example,STANDARD), you should use the Summary Ledger Template of your choice (for example, S_ACTDIV).This includes your Elimination Set, Minority Interest Set, Consolidation Ledger Set, and Consolidation Set.

• Because detail ledgers are not involved, journals will not be created. The Consolidation CalculationLog holds the information of how summary ledgers are updated.

• Your summary ledgers used for consolidation must be up to date before you process the consolidationso that, for example, any last-minute journals are rolled up to the summary ledgers properlywhen posted to its detail ledgers. Summary ledgers can be incrementally updated either throughjournal posting or by processing a separate Summary Ledger process.

Specifying Summary Ledger ConsolidationsTo set up consolidation on summary ledgers:

1. Specifying Summary Ledger Template

For all the summary ledgers that are used for consolidation, the Consolidation Log and ConsolidationEquity Temp records for summary ledger templates on the Ledger Template − Record Definitionspage must be specified. If you plan to use the Affiliate field to identify intercompany transactionbalances in summary ledger, your summary ledger must retain the Affiliate values.

2. Defining Elimination Sets on Summary Ledger

To consolidate on summary ledger, use the Elimination Sets page to define Elimination Sets basedon a summary ledger. You must specify both Ledger Template and the name of the summary ledgerso the system knows how to prompt for ChartField and ChartField Values.



If Affiliate value is kept in the summary ledger table and you want to use the Affiliate method of elimination,check the Match Affiliate Value option on the Elimination Lines page. If the Affiliate field is not one of thefields in the summary ledger template, the Business Unit value must be specified in the Elimination Set.

3. Defining Minority Interest Sets on Summary Ledger

Specify the appropriate Ledger Template and Ledger for the summary ledger on theMinor Int Source (minority interest source) page.

On the Minor Int Target (minority interest target) page, ensure that the Subsidiary Equity and ParentInvestment values are ChartField Value Sets based on the same summary ledger.

4. Defining Consolidation Ledger Set

Use the Consolidation Ledger Set page to specify the summary ledger names to beused for each Business Unit for consolidation.

5. Defining Consolidation Sets on Summary Ledger

Use the Journal Options page to specify the appropriate Ledger Template and Ledger for the summaryledger. The Ledger Set used for consolidation processing should be based on the same summary ledger.

6. On the Set Options page, ensure that Elimination Sets are based on the same summary ledger.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Defining a Ledger Template

Mapping Dissimilar Charts of AccountsYou can perform consolidations across an organization’s ledger balances when entities havedifferent ChartField structures. This is important when consolidations must be performed overentities that are not maintained in PeopleSoft General Ledger.

Create a Consolidation Chart of Accounts that represents a single, common reporting structure.This Consolidation Chart of Accounts must be mapped to each business unit’s disparate chartof accounts to be included in the consolidation rules.

The Consolidation Chart of Accounts can be structured at any level of summarization. This provides youwith the flexibility to define a Consolidation Chart of Accounts at a lower level of detail than is requiredfor reporting, but at a higher level than the individual business unit chart of accounts. Using trees overthe Consolidation Account, you can summarize up to the required level of external reporting.

The real value of Consolidations functionality is the ability to bring in data from many disparateledger systems and map to a common parent company chart of accounts.

To map dissimilar charts of accounts, use the ChartField Mapping Set component (CF_MAPPING_SET)and the ChartField Value Mapping component (CF_VALUE_MAPPING).

This section provides a review of a consolidation example and discusses how to:

• Define a ChartField Mapping Set.

• Map ChartField values.



Understanding a ConsolidationConsider this example of three mutually exclusive and disparate charts of accounts. Assume that all businessunits are set up in PeopleSoft General Ledger and there is a different Chart of Accounts for each setID.

SetIDMFG represents a manufacturing company,FS is a financial institution, andHC is a health care facility.

Acct # - MFG Acct # - FS Acct # - HC Account Descriptionby SetID

500000 500000 500000 MFG - Cost of GoodsSold

FS - Interest on Checking

HC - Cost of Goods Sold

510000 510000 510000 MFG - ProductionVar-Labor

FS - Interest on Savings

HC - Lost Charges −Unbillable

511000 N/A 511000 MFG - Production Var −Mat’l

FS - N/A

HC - Lost Charges -Supplies

512000 N/A 512000 MFG - Production Var −Ovhd

FS - N/A

HC - Lost Charges - Other

513000 N/A 513000 MFG - Purchase Price Var.

FS - N/A

HC - Purchase Price Var.

514000 N/A N/A MFG - Exchange RateVar.

FS - N/A

HC - N/A



Acct # - MFG Acct # - FS Acct # - HC Account Descriptionby SetID

520000 520000 520000 MFG - Inventory Scrap

FS - Interest − Wholesale

HC - Inventory Adj. −Obsolete

530000 N/A 530000 MFG - InventoryAdjustments

HC - Inventory Adj. -Other

540000 540000 540000 MFG − Discount Expense

FS - Group Insurance

HC - Discount Expense

610000 530000 610000

612000

613000

614000

MFG - Salaries

FS - Salaries

HC - Salaries

Notice the disparity in the numbering of accounts and the account descriptions. Account number500000 is used for a different purpose in each setID. For purposes of Consolidation, we must mapeach set of accounts to a single, common Consolidation Chart of Accounts.

This table illustrates a subset of a Consolidation Chart of Accounts to which individualaccounts by setID must be mapped:

ConsolidationAccount


Description

MFG FS HC

500000 Cost of Goods Sold 500000 N/A 500000

590000 Indirect Mfg. AndProd Costs

510000

511000

512000

513000

520000

530000

N/A N/A





Description

MFG FS HC

600000 Salary Expense 610000 530000 610000

612000

613000

614000

799000 Other General andAdministrativeExpenses

540000 540000 510000

511000

512000

513000

520000

530000

540000

801000 Interest on Deposits N/A 500000

510000

520000

N/A

898000 Foreign Exchange 514000 N/A N/A

As a result of the mappings, each setID has been correlated to a single, common Consolidation Chart of Accounts.

The example illustrates mapping at the setID level, which presumes that there are one or morebusiness units that share a common chart of accounts under a specific setID.

Pages Used for ChartField Mapping


ChartField Mapping Set CF_MAPPING_SET General Ledger, ConsolidateFinancial Data, LoadLedgers, ChartFieldMapping Set

Define which ChartFieldsare associated with mapping.

ChartField Value Mapping CF_VALUE_MAPPING General Ledger, ConsolidateFinancial Data, LoadLedgers, ChartField ValueMapping

Convert external data loadedin the Staging Table to thePeopleSoft Ledger Table.



Defining a ChartField Mapping SetAccess the ChartField Mapping Set page.

Chartfield Mapping Set page

Mapping Set Defaults

Ledger Template Populates Ledger Template ChartFields area when a LedgerTemplate is specified.

Ledger Template ChartFields

When a Ledger Template is specified this area is populated with the Ledger Template ChartFields.You can select which ChartFields are associated with mapping.

Option Select an Option and Value Set Name for each ChartField.



View Detail Click to go to the ChartField Value Mapping page.

Mapping ChartField ValuesAccess the ChartField Value Mapping page.

ChartField Value Mapping page

Target SetID Select value to indicate the setID you are mapping to.

Mapped Business Unit

Business Unit and SetID Select the Business Unit and setID you wish to map. Click the Addbutton to map additional Business Units. If the Business Units to beprocessed come from external source, then SetID values serve as ’groupname’ to group Business Units with the same chart of account structuretogether so they can share the mapping rules.

Mapped Values

Target Values ChartField Value is the Consolidation Chart of Accounts target ChartFieldvalue that the selected source values will be converted to.

Source Values SetID links the source value ranges with Business Units defined in the’Mapped Business Units’ scroll that have the same SetID value.

• SetID FromEnter the source SetID for those Business Unitsthat the Source Values apply to.

• Range From and Range To Enter the range of ChartField values forthe source SetID to map to the target ChartField value.

A conversion process reads the mapping setup and converts external data either loaded to the StagingTable, or to the Ledger table itself but under certain ledger names, and populate the PeopleSoftLedger Table. Consolidation is then performed on the Ledger Table.



Using EquitizationWhen the value of a parent’s investment in a subsidiary changes for the current year without a physicalevent (transaction), the parent’s investment in the subsidiary should be modified. No physical accountingevent has occurred, but the value of the parent investment has changed.

For example, net income of a subsidiary will increase the investment and owner equity of the parent.PeopleSoft General Ledger enables you to set up multiple Equitization rules for multiple businessunits that have complex parent-subsidiary relationships and create journal entries with a singleprocess. A ledger for a parent entity can be different from that of its subsidiary and, as one of theoptions, you can generate elimination entries for consolidated reporting.

This section discusses:

• Reviewing an Equitization example.

• Reviewing components of the Equitization process.

Reviewing an Equitization ExampleIn this example, Company M0004 owns 70% of company M0002. In January of 2003, M0002 had a netincome of 100 in period 1. An Equitization rule is set up to select expense and revenue accounts as theEquitization source, and investment and equity income as the Target (debit and credit, respectively).The Equitization process creates journals to book 70 to the M0004 ledger investment account and−70 to its equity income account, as indicated by the entries in this illustration.

Equitization Source andTarget Account Types

M0002 M0004

N/A Period 1 Period 1

Cash, Receivables, and so on 100 230

Investment in M0002 N/A 70 a

Revenues <1000> <2230>

Expenses 900 2000

Income before Equity Adjustment <100> <230>

Equity Income N/A <70>a

Net Income <100> <300>



Viewing an Example of Multiple Parent/Subsidiary Ownership

If, in addition to the M0002 to M0004 relationship, F0001 owns 20% of M0002 and 60%of M0004, the equity income from subsidiaries for F0001 will be 200, with 20 from M0002and 180 from M0004, as indicated by theb entries:

Equitization Sourceand Target Account

Types

M0002 M0004 F0001

N/A Period 1 Period 1 Period 1

Cash, Receivables, and soon

100 230 N/A

Investment in M0002 N/A 70 a 20 b

Investment in M0004 N/A N/A 180 b

Revenues <1000> <2230> <1500>

Expenses 900 2000 1000

Income before EquityAdjustment

<100> <230> <500>

Equity Income N/A <70> a <200> b

Net Income <100> <300> <700>

The Equitization process will determine the correct sequence to process. It will equitize fromM0002 to M0004 and F0001 first, and then M0004 to F0001, so that the 70 from the firststep will be included as part of the net income in the second.

Creating Elimination and Minority Interest Entries

An option of the Equitization process enables you to generate elimination and minority interestentries as by-products. If specified, Equitization creates the elimination entries that reverse Targetamounts. As in the Consolidations process, these entries will go to the proper elimination businessunits in the consolidation tree and are used in consolidated reporting. In the following example,elimination entries are generated for elimination business unit ME001.



Elimination Entries M0002 M0004 ME001

N/A Period 1 Period 1 Period 1

Cash, Receivables, and so.

100 230 N/A

Investment in M0002 N/A 70 a <70) c

Minority InterestLiabilities

N/A N/A <30> c

Revenues <1000> <2230> N/A

Expenses 900 2000 N/A

Income before EquityAdjustments

<100> <230> N/A

Equity Income N/A <70> a 70 c

Minority InterestExpenses

N/A N/A 30 c

Net Income <100> <300> 100

If year-to-date elimination for investment is handled in Equitization, the Consolidations processneed not and should not generate elimination again.

Offsetting the Source

This option creates entries to offset the equitized source amount for subsidiary entities.It may be useful for special reporting purposes.

Equitized Source OffsetEntries Account Types

M0002 M0004

N/A Period 1 Period 1

Cash, Receivables, and so on. 100 230

Investment in M0002 N/A 70 a



Equitized Source OffsetEntries Account Types

M0002 M0004

Revenues <1000> <2230>

Expenses 900 2000

Equity Income N/A <70> a

Retained Earnings Offset 100 d N/A

Equalized Income Summary <100> d N/A

Reviewing Components of the Equitization ProcessThe Equitization process includes the following components:

Data Data used for calculation comes from ledgers for all the subsidiary businessunits involved. Different business units can use different ledgers so longas they are within the same physical ledger table (that is, share the sameLedger Template) and the same Currency Code.

For example, M004 uses ledger ACTUALS in Equitization, which specifiedthe U.S. dollar as the transaction currency. M002 uses its U.S. dollar ledgerREPORTS in the process since its primary ledger ACTUALS uses the Canadiandollar as its base currency. On the Ledger Sets page, define which ledgers areused in the process within each business unit, keyed by consolidation trees.

Scope You specify which business units to cover during Equitization by creatinga business unit tree. You also define the ownership relationships on theSubsidiary Ownership page, specifying subsidiary entities and parent entitieswith their percentage of ownership. Any parent/subsidiary sets included in thebusiness unit tree will be included in the Equitization process.

If you are also performing Consolidations, Equitization can sharethe consolidation tree with the Consolidations process, as wellas the ownership sets, if applicable.

Rules On the Equitization Rules page, you can specify the Equitization Source,Target, Subsidiary Offset, and Minority Interest entries. You can then groupmultiple Equitization rules together on the Equitization Group page.

Process You specify run options for the Equitization background process on theDefining Equitization Rules page. PeopleSoft General Ledger will createjournal entries based on the Equitization rules and scope, and you can edit thesejournals as part of Equitization. Since Equitization is a year-to-date process,the system will create reversal journal entries for any mid-year processes.



If you need to reverse the Equitization and unpost and delete all the journals,you can use theUndo Previous Process on the Running Equitization page. Ifthe process fails, unlock all journals before rerunning unpost.

See Also

Chapter 16, “Performing Financial Consolidations,” Defining Equitization Rules, page 349

Defining Business Unit Trees and EliminationUnits for Equitization

If you are running the Consolidations process as well as Equitization, you can use the Consolidationsbusiness unit tree to specify which business units to include in the Equitization process. Eliminationbusiness units must be part of the tree in order for elimination entries to be generated. UnlikeConsolidations, the order in which Equitization business units are processed is determined by ownershipsets (that is, who owns whom) and not by their location in the tree.

See Also

Chapter 16, “Performing Financial Consolidations,” Defining Consolidation Trees, page 317

Chapter 16, “Performing Financial Consolidations,” Setting Up Elimination Units, page 319

Specifying Ledgers for Each Business Unit in an EquitizationFor each Business Unit involved in the Equitization process, you can specify one ledger asthe source or target ledger, the same as you would for the Consolidation process. You specifythe ledger for a business unit on the Ledger Sets page.

See Also

Chapter 16, “Performing Financial Consolidations,” Specifying Consolidation Ledgers, page 320

Defining Ownership Sets for EquitizationUse the Subsidiary Ownership page to define ownership sets, which indicate relationships among theparent company, subsidiary business unit, and any other minority owners.

Use the Equitize check box on this page to indicate whether Equitization should berun for specified parent entities.



See Also

Chapter 16, “Performing Financial Consolidations,” Defining Subsidiary Ownershipand Minority Interest Sets, page 325

Defining Equitization RulesYou can define multiple Equitization rules for a process. For example, you can define one rulefor subsidiary net income and another rule for unrealized gain and loss. Equitization will processall the rules in one ownership set and then proceed to the next set.

To define equitization rules, use the Equitization Rules component (EQUITIZATION_RULE).


• Specify the Equitization source.

• Specify the Equitization target.

• Specify the subsidiary offset.

• Specify minority interest.

Pages Used to Define Equitization Rules


Source EQTZ_RULE General Ledger, ConsolidateFinancial Data, Equitization,Equitization Rules

Define your EquitizationRules.

Target EQTZ_TARGET General Ledger, ConsolidateFinancial Data, Equitization,Equitization Rules, Target

Specify ChartKey valuesand details for creatingEquitization entries.

Subsidiary Offset EQTZ_OFFSET General Ledger, ConsolidateFinancial Data, Equitization,Equitization Rules,Subsidiary Offset

Define an Equitizationoffset, which is used to offsetthe Equitization sourceand becomes part of thesubsidiary entities.

Minority Interest EQTZ_MIN_INT General Ledger, ConsolidateFinancial Data, Equitization,Equitization Rules, MinorityInterest

Specify values for minorityinterest entries.

Specifying the Equitization SourceAccess the Source page.



Equitization Rules - Source page

Ledger Template Specify the template to limit ChartFields applicable to settingup the Equitization Rule.

Equitization Source

Chartfield Value Set Defines which entries in the ledgers of the subsidiary will beselected as the Equitization source.

Update/Create Click the link to access the ChartField Value Set page if youwant to edit or create a new set.

See Also


Specifying the Equitization TargetAccess the Target page.

Equitization - Target page



Parent Investment and Investment Offset

Field Name For a parent investment, you must specifyAccountor AltAcct for thisrequired ChartField, and you must specify a value for it.

Option Specify either aConstantvalue orRetainthe ledger value.

Value This field is activated only if the Option field specifiesConstant. Enter aChartField value for the parent investment or investment offset.

Exch Rate Type(exchangerate type)

The system defaults to the exchange rate you are currently using,but you can also select a specific one.

The system will summarize source amounts (debits) at the level specified by the parent investmentChartField and book them to the account specified in the Value field. However, it will create onlyone row (with the investment offset Value field) for the credit side.

If the Affiliate ChartField is used in the ledger, the system will populate the Targetentries with the subsidiary business unit value.

When creating an Equitization Rule, you can establish one or more Investment andEquity offsets by setID and Business Unit.

Specifying the Subsidiary OffsetAccess the Subsidiary Offset page.

Equitization - Subsidiary Offset page

You can use these accounts as an income summary on the subsidiary. The Equitization Summarywill represent the gross change in an individual subsidiary’s value. In the case of net income, youcan place the value in the minority interest definition for equity. In this way you avoid a minorityinterest elimination entry for each detail value in the net income node.

See Also

Chapter 16, “Performing Financial Consolidations,” Specifying the Equitization Target, page 350



Specifying Minority InterestAccess the Minority Interest page.

Equitization - Minority Interest page

If you select Create Equitization Eliminate’n (create equitization elimination) , the system will generateelimination entries to eliminate the Equitization target entries. If you want to generate Minority Interestentries, specify their value and the system will generate Minority Interest as part of the elimination.Elimination entries are booked to elimination business units in the consolidation tree.

See Also

Chapter 16, “Performing Financial Consolidations,” Specifying the Equitization Target, page 350

Defining an Equitization Group and Journal OptionsWithin an ownership set, the consolidation process will create one journal for each business unitinvolved. If rounding errors occur, Equitization will adjust the amount of the last journal line of eachjournal to make the total debit amount equal to the total credit amount.

To define equitization group and journal options, use the Equitization Groupcomponent (EQUITIZATION_GROUP).

This section discusses how to create an equitization group.

Page Used to Define an Equitization Group and Journal Options


Equitization Group EQTZ_GROUP General Ledger, ConsolidateFinancial Data, Equitization,Equitization Groups,Equitization Group

Specify Equitization rulesand journal options.



Creating an Equitization GroupAccess the Equitization Group page.

Equitization Group page

Journal Options

Journal ID Mask Enables you to specify a prefix for naming Equitization journals. A10-character alphanumeric ID identifies journals. The system automaticallyappends the prefix you specify to the journal IDs. For example, if you specifyyour Journal ID Mask to beEQTZ, your Equitization Journal IDs might beEQTZ0001, EQTZ0002, and so on. Alternatively, the valueNEXTcausesPeopleSoft General Ledger to assign the next available journal ID numberautomatically. It isvery importantto reserve a unique mask value forConsolidations to ensure that no other process will create the same Journal ID.

Journal Source Any valid Sources table entry.

Doc Type(document type) Required if Document Sequencing is enabled in order to indicate thebusiness purpose of your transactions. Document Sequencing requiresthat you have a document type for all the journal entries you createto record the equitization change. If you have not enabled DocumentSequencing in your system, this field will be unavailable.

Equitization Rules

Select one or more rules from those you defined previously on the Equitization Rulescomponent and include in your equitization.

Equitization Reversal

Select either the Beginning of Next Period or End of Next Period for reversal journal entries.



See Also


Performing EquitizationOnce you define Equitization rules, an Equitization group, and related options, youcan proceed to perform an Equitization.


• Initiate Equitization processing.

• View the Equitization Process Log.

Pages Used to Perform Equitization


Equitization Request EQTZ_REQUEST General Ledger, ConsolidateFinancial Data, RequestEquitization, EquitizationRequest

Initiate the COBOLEquitization processGLPQEQTZ.

Equitization Process Log EQTZ_PROCESS_ING General Ledger, ConsolidateFinancial Data, ReviewResults Online, EquitizationProcess Log

View the Keys to use formatching on the RunEquitization page.

Initiating Equitization ProcessingAccess the Equitization Request page.



Equitization Request page

Equitization Parameters

SetID SetID for the Equitization.

Currency Currency used in the Equitization.

Equitization Group Defines what Equitization rules and journal options apply.

As of Date Serves as a point of reference for determining the year and period toequitize for each ledger involved. If business units use different calendars,system will evaluate the year and period for each. It is also used toaccess any effective-dated setups during the process.

Equitization Options

Process Equitization Required for the system to create Equitization journal entries. Journals willalways be posted because ownership sets that will be processed later maydepend on the entries to ledgers for earlier ownership sets.


Includes balances of Adjustment Periods that are specified in theEquitization Group when processing Equitization.

Create Calculation Log Generates a calculation log that contains pertinent information regardingthe Equitization process. Once the system creates the log, you can runthe Equitization Calculation Log (GLS2008) SQRs.

Edit Journal(s) When an edit error occurs, you can use the Journal Edit Error page toidentify the error and correct it before you process the Equitizationagain. The system clears journals from the original process beforeregenerating. If Journal Edit errors occur, you can identify them through



the Journal Entry pages. To correct these errors, you must undo theprocess, correct the problem, and re-run Equitization.

Undo Previous Process Clears the effect of prior processing. The system will unpost all journals(including reversal entries), delete journals, and delete the calculationlog from the last process. You can perform the Undo process by itself,or select it with the Process Equitization option. If the process fails,unlock all journals before rerunning unpost.

Undo - Do Not DeleteJournals

The Undo process will not delete unposted journals. If you selectthis option and have journals from the Consolidation process thathave not been posted, you can accidentally post those journals andcause elimination to be double booked.

Note. If the process aborts during an undo, unlock the journals for the process instancebefore rerunning the undo process.

Scope of Equitization

Tree Select the appropriate tree.

Scope Specify if you want to:

• Process the Whole Tree

• Process a Level

• Process a Tree Node

Level Processes all business units at and below the particular tree levelthat you select in the edit box.

Node Processes business units at and below the particular tree nodethat you select in the edit box.

Tree Effective Date Option

Use As of Date Uses the date defined for the Equitization.

Use Override Date If you want to override the tree As of Date, enter a date in theTree Override Date field provided.

For the Equitization process to identify the correct journals to unpost and delete, informationon the Run Equitization page must match the information specified for a previous process.The items you must match are setID, Currency, Equitization Group, As of Date, and Scope ofConsolidation. This information is stored in a process log.

See Also


Chapter 16, “Performing Financial Consolidations,” Viewing the Equitization Process Log, page 357

Chapter 16, “Performing Financial Consolidations,” Initiating Consolidation Processing, page 333



Viewing the Equitization Process LogAccess the Equitization Process Log page.

Equitization Process Log page

Select an Equitization Group, Tree, and the start date for the list of processes as Search criteria. The firstrow of each process contains the keys that you use for matching on the Run Equitization page. The fieldson this page are the same as those found on the Run Equitization page, with the addition of Instance,DateTime, and Request No. These fields are created after the process is completed.

See Also

Chapter 16, “Performing Financial Consolidations,” Performing Equitization, page 354

Producing Consolidation and Equitization ReportsPeopleSoft General Ledger delivers standard consolidation and Equitization reports designed to providethe kind of business information many companies need. Running a report entails selecting it from amenu and entering any necessary parameters. Once you have entered the report parameters, you useProcess Scheduler to manage the processes, track the status, and generate the report.

Pages Used to Produce Consolidation and Equitization Reports


Elimination Sets Report RUN_GLS2000 General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets,Elimination Sets Report

Specify run parameters forthe Elimination Sets Reportproduced by the GLS2000SQR.

Lists all definitions of aspecified elimination set forfinancial consolidations.

Minor Interest Sets Report RUN_GLS2001 General Ledger, ConsolidateFinancial Data, Reports,Minority Interest Sets,Minority Interest Sets Report

Specify run parameters forthe Minority Interest SetsReportproduced by theGLS2001 SQR.

Lists the minority interestset definitions for financialconsolidations.



Page Name Object Name Navigation UsageConsolid Set Report RUN_GLS2002 General Ledger, Consolidate

Financial Data, Reports,Consolidation Definition,Consolidation Set Report

Specify run parameters forthe Consolidation DefinitionReport produced by theGLS2002 SQR.

Lists the options andcontrols that tell the generalledger how to process aconsolidation.

Elimination Out of BalanceReport

RUN_GLS2003 General Ledger, ConsolidateFinancial Data, Reports,Elimination Out of Balance

Specify run parameters forthe Elimination Out ofBalance Report produced bythe GLS2003 SQR.

Lists detailed informationabout the eliminationsets and ledger amountsprocessed for a consolidationrequest.

Minority InterestEliminations andAdjustments Report

RUN_GLS2004 General Ledger,Consolidate FinancialData, Reports, Minority IntElim/Adjustment, MinorityInterest Eliminations andAdjustments Report

Specify run parametersfor the Minority InterestEliminations andAdjustments Reportproduced by the GLS2004SQR.

Lists the results of minorityinterest calculations for aconsolidation request basedon the combination ofbusiness units present in theconsolidation tree.

Equitization Rules Report RUN_GLS2006 General Ledger, ConsolidateFinancial Data, Reports,Equitization Rules,Equitization Rules Report

Specify run parameters forthe Equitization RulesReportproduced by theGLS2006 SQR.

Lists the definitioninformation and purpose forthe Equitization rule.

Subsidiary OwnershipSets Report

RUN_GLS2007 General Ledger, ConsolidateFinancial Data, Reports,Ownership Sets, SubsidiaryOwnership Sets Report

Specify run parameters forthe Ownership Set Reportproduced by the GLS2007SQR.

Lists detailed information ofan ownership set.

Equitization CalculationLog Report

RUN_GLS2008 General Ledger, ConsolidateFinancial Data, ReviewResults Online, EquitizationCalculation Log,Equitization CalculationLog Report

Specify run parameters forthe Equitization CalculationLog Reportproduced by theGLS2008 SQR.

Lists Equitizationcalculation details byprocess instance.



See Also

PeopleTools PeopleBooks: PeopleSoft Reporting Tools

Using the Ledger Interface UtilityPeopleSoft General Ledger users often need to send the contents of their regional databases to acorporate location where the data is consolidated into a single database. Using PeopleSoft ApplicationMessaging, the Ledger Interface Utility can send data from either PeopleSoft or non-PeopleSoft databases.The Ledger Interface Utility is delivered with PeopleSoft General Ledger.


• Set up the Ledger Interface Utility.

• Publish ledger data.

• Load external ledger data.

• Review the process.

Pages Used to Set Up the Ledger Interface Utility


Publish Ledgers Request LED_PUB_REQ General Ledger, ConsolidateFinancial Data, LoadLedgers, Publish Ledgers,Publish Ledgers Request

Launch the Ledger PublishProcess (GL_LED_PUB).

Load Ledgers Request LED_LOAD_RQST General Ledger, ConsolidateFinancial Data, LoadLedgers, Request LedgerLoad, Load Ledgers Request

Load data from PeopleSoftor non-PeopleSoft databasesto the corporate databaseusing ApplicationMessaging.

Setting Up the Ledger Interface UtilityThe Ledger Interface Utility transfers both detail and summary ledgers from one database to another.The utility extracts multiple ledger data from a regional database, sends it to the corporate location,and provides for ChartField mapping of detail ledgers. This is done for each regional database inpreparation for consolidating all regional data into one corporate database.

PeopleSoft Application Messaging requires that the source and target databases have identicalledger table structures in order to communicate. This is true for all publish and subscribeapplication messages. Ledger ChartFields must be the same for summary ledgers. The scopeof the Ledger Interface Utility is limited to the transfer of data.

Setting up the utility to send regional databases to a corporate location requirescompleting several tasks as follows.



Task 1 - Define Message Nodes

Message nodes represent publishing or subscribing entities such as databases or application servers, and theyare most often associated with a database name. Both corporate and regional locations need to define messagenodes. Corporate defines its own local node and one remote node for each regional location that sends data.Each regional location defines its own local node and defines one remote node for the corporate location.

Do the following to define the necessary message nodes:

• Define a local message node. As delivered, the Ledger Interface Utility publishes data tothe standard PSFT_EP message node. Rename the standard local node with a unique nodename of your choosing that is associated with your database.

• Verify that the node, as you renamed it, is the local node. There can be only one local node at a location.If you attempt to save a second local node, you will receive an error message.

• Define remote message node locations. A region defines one remote node for its corporatelocation, and the corporate location defines multiple remote nodes, one for each regional databaseto be consolidated. If the corporate list is missing a URL for one of the regional databases,the corporate location will not receive the data for that region.

Task 2 - Define the Message Channel

A message channel is a logical group of messages. Each message must belong to one (and only one) messagechannel, which specifies a routing. Both publishing and subscribing nodes use this channel.

To define the necessary message channel:

• Use the delivered message channel named LEDGER.

• As delivered, the Ledger message channel contains one routing rule for the standard PSFT_EPmessage node. You can delete the delivered routing rule and create rules that apply to yourdatabases. Regional and corporate locations define different routing rules.

• At the local regional location, define one routing rule with a message node name for yourcorporate location, withPublish Toas the direction.

• At the corporate location, define a routing rule with one message node name for each regional database thatis involved in the consolidation. All routing rule definitions must beSubscribe From. If the corporate list ismissing a routing rule for one of the regional databases, corporate will not receive data for that region.

Task 3 - Define the Message

A Ledger Interface Utility message contains a general ledger database. The message is the vehicle of transportthat carries the database from the regional entity at one URL to the corporate entity at another URL.

Application data is inserted into the message according to the records that are specified in themessage definition. Regional message definitions must match corporate message definitions.If you change your table in the database, the changes are automatically inherited by themessage definition as long as table names remain the same.

Do the following to define the message:

• View the LEDGER_LOAD message. Because consolidation does not support PeopleSoftProjects or Commitment Control, no ledger record names for Projects or Commitment Controlare listed under LED_PUB_REQ in the message definition.



• PeopleSoft recommends that you keep the delivered record names in the LEDGER_LOAD Messagedefinition because changing them is considered a customization. If you must use a different table name, thetable name listed below LED_PUB_REQ must match the ledger table name on the ledger template. Fordetail ledgers, the record definitions of your new ledger table and your staging table must be identical.

• Activate the LEDGER_PUBLISH message at regional and corporate offices.

Task 4 - Create Staging Tables

Because summary account ChartField values are the same for regional and corporate summary ledgers,the Summary ledger subscription process writes the subscribed data directly into the consolidatedledger table. Access the Setup Financials/Supply Chain, Business Unit Related, General Ledger,Definition page and select theAllow Ledger Load Updates check box.

Because detail ledgers frequently contain account ChartField values that differ between regional andcorporate entities, the regional accounts need to be mapped to corporate accounts. To accomplish themapping, detail ledger data is subscribed into staging tables. A ChartField mapping process reads thestaging table, maps it, and writes the resultant data to the consolidated detail ledger table.

Do the following to create staging tables:

• Define staging table names at the corporate location. For detail ledgers, create record definitions for thestaging tables that are identical to the record definitions of their corresponding ledger tables.

• At the corporate location, create a message record alias for each staging table. The alias namesfor the corporate node must match the alias names at the remote nodes.

Task 5 - Publish the Ledger Data

Publishing ledger data is done at regional locations. To publish a regional database, use thePublish Ledger page to select criteria and process options.

Task 6 - Subscribe from the Ledger Data

Using Application Messaging, data is published by initiating a process request on the regionalgeneral ledger database. At the corporate location, the subscription process is run automaticallyon the application server of the subscribing node.

Summary ledger data is written to the summary ledger file, and detail ledger data is writteninto the staging tables that are defined at the corporate location.

Before you run the ChartField mapping process (Task 7), verify the detail ledger data. Adda view to the query tree for the staging table and save it so that you can query the stagingtable to ensure that the data is written properly.

Task 7 - Perform ChartField Mapping

Regional detail and summary ledgers must have the same ChartFields and use the same calendarwhen you assign them to a business unit. Because account numbers often differ between detail andsummary ledgers, run the ChartField Mapping process against the detail ledger data that is writtento the staging tables. After mapping, run the consolidation process.



For detail ledgers, the system checks the staging table alias against the ledger template definition. If thestaging table alias is pointing to the ledger template definition, it is possible for data to be written to anapplication table in error. To prevent such an error, the subscription process rejects any message whosestaging table alias points to an application table that is defined in the ledger template.

If the staging table alias does not point to the ledger template definition, the system writesdata into the staging table as specified by the alias.

Do the following to perform ChartField mapping:

• Verify that the proper detail ledger data resides in the staging table (recommended). Addviews to the query tree for the staging tables and save them only once. Query the stagingtables to verify that the data is written properly.

• Run the ChartField mapping process against the staging tables.

Note. For summary ledgers, the system writes data directly to the application table only ifthe Allow Ledger Load flag on the ledger group is enabled.

Task 8 - Load Ledger Data

Loading ledger data is done at the corporate location. To load ledger data, use the LoadLedgers Request page to select criteria and process options.

Publishing Ledger DataAccess the Publish Ledger page.

Select run criteria and processing options. An Application Engine process called GL_LED_PUB extracts ledgerdata from the selected ledger table and publishes an application message according to your request options.

Loading External Ledger DataAccess the Load Ledgers Request page.

Select run criteria and processing options. An Application Engine process called GL_LED_LOAD loadsexternal ledger data into the corporate database through Application Messaging.

Consolidation of ledger data is done at the corporate location.

Note. Consolidation does not support PeopleSoft Projects or Commitment Control.

See Chapter 16, “Performing Financial Consolidations,” Performing Consolidation, page 332.

Reviewing the ProcessThis section describes important things to consider concerning your detail ledgers, summary ledgers,and the process setup before you use the ledger interface utility process.

Detail Ledgers

Considerations:



• Detail ledger ChartField values from regional databases can differ from the corporate database because thedata is transmitted to the staging table. The ChartField mapping process reconciles these differences.

• For staging tables, add and save a view to the query tree. Query the staging table to verify thatthe data loaded properly before performing ChartField mapping.

• Regional detail ledgers must use the same calendar when you assign them to a businessunit. Verify the calendar on the Ledgers for a Unit page.

• Regional detail ledgers must have the same ChartFields when you assign them to a BusinessUnit. Verify detail ledger ChartFields by navigating to the Detail Ledger Group - ChartFieldpage: General Ledger, Ledgers, Ledger Groups, and select the ChartField tab. The Detail LedgerDefinition Report (FIN0022) also shows the structure of the detail ledgers.

Summary Ledgers

Considerations:

• ChartField values must be valid in both corporate databases and regional databases for the summary ledger.

• Regional summary ledgers must use the same calendar when you assign them to a businessunit. Verify the calendar on the Ledgers for a Unit page.

• Regional summary ledgers must have the same ChartFields when you assign them to a businessunit. Verify summary ledger ChartFields using the Summary Ledger Definition report (GLC1000),which shows the ChartField structure of summary ledgers.

Setup

To complete setup and verify the publication and subscription of information refer to the PeopleToolsdocumentation for the PeopleSoft Integration Broker and see the section on using Integration Broker Monitor.




CHAPTER 17

Managing Interim and Year-End Closing

This chapter provides an overview of interim and year-end closing and discusses how to:

• Perform interim closing.

• Perform year-end closing.

• Define closing rules.

• Run the Close Application Engine process (GLPCLOSE).

• Process an undo close.

• Produce interim and year-end closing reports.

Understanding Interim and Year-End ClosingThis section discusses:

• Interim versus year-end closings.

• Single versus multiple retained earnings accounts closings.

• Closings that use book codes and balance sheet indicators.

Interim Versus Year-End ClosingsAlthough most companies need to close profit and loss accounts to retained earnings only once ayear; other companies may close as often as once a day. PeopleSoft General Ledger enables you torun closing as frequently as you need throughinterim (net income) closings. The system also providesyear-end closing on the Account and Alternate Account (statutory) ChartFields.

Interim and year-end closings are similar in that they both close profit and loss (P/L) accounts toretained earnings. However, there are differences in the capabilities of each type of closing. Thissection identifies the differences and similarities of the two types of closings.

This table describes the differences between interim and year-end closing:


Managing Interim and Year-End Closing Chapter 17

Interim Close Year-End Close

Enables you to close periods within a fiscal year (forexample, daily or monthly) on the Account ChartField.

Enables year-end close. Closes the year that you specifyon the Account ChartField, the Alternate AccountChartField, or both.

Enables you to select some or all P/L accounts to beclosed.

Unless the Set Default Retained Earnings option is set toOff,all P/L accounts are closed.

Note. This option is not available when the BalanceSheet Indictor option is selected.

Does not carry forward closing balances. Carries forward closing balances to beginning balancesfor balance sheet accounts.

If closing is not performed forall book codes and balancesheets, closing balances carried forward to beginningbalances are balanced for only the set of accounts definedby the closed book codes or the closed balance sheets.

Creates journal entries that you post during or after theclosing process.

Directly updates the ledger.

Optionally, creates journal entries for those companiesthat require journal entries for any transaction that affectsledger balances.

Creates optional offsetting entries into alternativeChartField values.

Creates offsetting entries into source P/L ChartFieldvalues in the ledger.

If using interim close with offsetting entries, the you mustselect the offset to the retained earnings account as thetarget retained earnings for the year-end close.

Closes selected adjustment periods. Automatically closes all adjustment periods for the year.

Includes Account in P/L ChartFields. Includes Account or Alternate Account in P/LChartFields.

Single Versus Multiple Retained Earnings Account ClosingsIn either interim or year-end closings, PeopleSoft General Ledger enables you to close P/L to asingle retained earnings account or to multiple retained earnings accounts.

Closing to a Single Retained Earnings Account

When you close to a single retained earnings, you can close all P/L accounts to a single retainedearnings account. You can also close the P/L accounts to a single retained earnings accountand break the amount down by other ChartFields (for example, Project or Department). Thisflexibility enables you to track profit and loss more effectively.


Chapter 17 Managing Interim and Year-End Closing

All closing rules require the Account ChartField, the Alternate Account ChartField, or both. You can closeonly these ChartFields, or you can combine the Account ChartField with other ChartFields such as Department,Product, or Project ID. For example, if you want to track department-specific retained earnings, you combinethe Account ChartField with the department ChartField. During the closing process, the department totals stillclose to a single retained earnings account, but the system generates separate ledger entries for each department.

Closing to Multiple Retained Earnings Accounts

When you close to multiple retained earnings, you distribute P/L to multiple retained earnings accountsbased on appropriate criteria for the business. For example, you might distribute profit and loss basedon specific P/L accounts or based on departments. You close a specific group of ChartField values toa single retained earnings account, but you close other specific groups of ChartField values to othersingle retained earnings accounts. ChartField value sets facilitate this process.

ChartField value sets enable you to define combined ChartField values that the system uses for source dataduring the PeopleSoft General Ledger closing process. For example, you can create one ChartField value setfor the income statement accounts used in interim closing and another set to use in year-end closing. When youdefine closing rules for the interim close or the year-end close, you select the appropriate ChartFields value sets.

Here is an example of closing to multiple retained earnings accounts. In this example, P/L accounts41000 − 410010 and 410015 and 410016 close to retained earnings account 360100, and P/Laccounts 410020 − 410029 close to retained earnings account 360200.

P/L accounts ChartFields Value Set Retained Earnings Account

41000

through

410010

CFVS 1 360100

410015

410016

CFVS 1a

410020

through

410029

CFVS 2 360200

You can set up value sets that combine P/L account with the Department ChartField and the ProductChartField, or use whatever combination you need to track profit and loss.

See Also




Closings That Use Book Codes and Balance Sheet IndicatorsBook codes are both an account attribute and balancing ChartField. They can be used to groupAccount ChartField values for the recording of transactions under different accounting rules in thesame business unit and ledger. For example, you can use them to record corporate versus localtransactions when different accounting rules apply. In this case, you might create the book codesC, L, andB to classify accounts as corporate (C), local (L), or both (B).

For accounts with book code values that can be overridden, you must select a book code to avoidreceiving a warning message. A book code is fixed for an account that cannot be overridden, andthe system enters it automatically. If you retain a book code for the offset, you must also retain it forthe retained earnings ChartFields, and it must be a book code that can be overridden. For the defaultretained earnings account, you can select only a book code that can be overridden.

In addition, the PeopleSoft system comes with standard balancing attributes for Account ChartFieldvalues to segregate and maintain separate transactions within a business unit and ledger forBS (balance sheet) andOB (off balance sheet) transactions.

Use book code and balance sheet indicators to create subsets or groups of accounts within a ledger thatcorrespond to different accounting rules. When the closing edit is run, the system verifies the valuesof the book code and balance sheet indicator for the retained earnings account.

When a retained earnings book code is fixed, either the account cannot be overridden or a fixed bookcode is entered. Only the entries from the source with the same book code are closed. Similarly, only theentries with the same balance sheet indicator value as the retained earnings account are closed.

Consider the preceding example. To close subsets separately, you must create ChartField value sets that specifythe accounts that the system closes together. You use a book code, a balance sheet indicator, or both.

ChartField Value Set Account Book Code Balance SheetIndicator

CFV1 Account RollupINCSTMNT

B BS


B OB


C BS


C OB


L BS


L OB



Note. Check balances by running a query on period0 for the book codes used for year-endclose. Year-end close carries forward all ending balances to beginning balances for balance sheetaccounts, including balances for both closed and open book codes.

Performing Interim ClosingThis section provides an overview of interim closing and discusses how to:

• Perform interim closing procedures.

• Interpreting the results of interim closing.

Understanding Interim ClosingThe source for interim closings is journals only. Interim closing is similar to year-end closing except that itdoes not create carry-forward balances. Other differences are discussed earlier in this chapter.

See Chapter 17, “Managing Interim and Year-End Closing,” Interim Versus Year-End Closings, page 365.

The interim closing process provides flexibility in tracking profit and loss by enabling you to:

• Close frequently.

You can transfer net income to retained earnings as often as needed. For example, financial institutions mayneed to close P/L to retained earnings daily, but other companies may close to retained earnings monthly.You include only the transactions that have been posted to the specified period since the last interim close.

• Maintain closing consistency.

The interim closing process depends on a consistent use of periods for interim closing throughoutthe year. You must maintain daily, monthly, or quarterly interim closings on a consistent basis,or you must perform a closing undo after any ad hoc interim close. You must also complete allinterim closes for the year. The year-end close uses the specified interim close offset account as thetarget retained earnings account. The offset is a contra-equity account that is zeroed-out against theP/L accounts to arrive at the correct year-end retained earnings amount.

• Integrate interim and year-end close.

When you integrate the interim close into the year-end close process, the offset account in interimclose is similar to an income summary account (which is an intermediate account used to summarizerevenue and expense accounts before posting net income to retained earnings). The interim closeprocess is similar to posting net income to retained earnings. Use of the interim close offset accountas the target account in year-end close is similar to summarizing the revenue and expense accountsto the income summary account. The offset account must net to 0 after the final interim close forthe applicable period and the year-end close processes are run. You verify the results when theyear-end close process results in a 0 balance for the interim close offset account.

• Identify specific P/L distribution accounts.

You can identify the specific accounts to close, as well as the retained earnings accounts towhich they are distributed. These can be the same as the retained earnings accounts thatyou use for year-end close. Furthermore, you can close only part of the chart of accounts(rather than the entire ledger) during an interim close.



• Maintain an audit trail.

You maintain the audit trail by creating alternative offsets to the retained earnings entries.In addition, you identify the offset account values.

• Create supporting journal entries.

The system creates journals from the results of the interim close. Create a journal ID maskfor these transactions to easily identify the closing journals.

• Select target currency for retained earnings.

If you manage financial information in multiple currencies, you can select the currencyfor the retained earnings amounts.

Note. If you need to undo a close, the system uses the journal entries to back outthe changes made by the interim close.

Important! If you use multiple currencies, perform a revaluation of the currency balancesbefore you run the interim closing process.

Performing Interim Closing ProceduresInterim closing involves three major tasks.

To perform an interim close:

1. Define ChartField value sets.

You define the sets of values for the ChartFields that you want to use as the source for the interimclosing. These can be the same value sets of ChartFields that you use for year-end closing or differentvalue sets. They can include some or all the values in your chart of accounts.

Specifically, you create ChartField value sets for the ChartFields that are closed to retained earnings.(ChartField value sets are defined on the ChartField Value Set page.)

To enhance performance, use fewer ChartFields in the ChartField value set (CVS) whenever possible.Also, use fewer ChartField combinations. For example, if all other things are equal, it takes less time toclose from five CVSs,all with ACCOUNT, DEPTID, and PRODUCT, than to close from three CVS withACCOUNT, DEPTID, and PRODUCT and two CVSs with ACCOUNT, DEPTID, and OPERATING UNIT.

2. Define closing rules.

Define the rules for the interim close. You define closing rules in the ClosingRules component (CLOSE_DEFN).

Specifically, you need to identify:

• Which time frame to close (for example, beginning of year to current date).

• Which P/L accounts to close to the various retained earnings accounts.

• Which currency to use as the target currency.

• Which adjustment periods to close (or whether to exclude them at all).

• Which book codes and balance sheet indicators to close (or whether to close to anaccount that can be overridden and retain book codes).



• Whether to edit, budget-check, and post journals.

• Whether to create offset accounts.

3. Run a closing request.

You run interim close using the Close Request page. When you request that theinterim close be processed, you identify:

• Which ledger group or ledger (or both) to close.

• Which closing rule to use.

• Which date to use as the as-of date for the closing.

• Which business units to close.

You can undo a close, if necessary, by using the procedures described later in this chapter.

See Chapter 17, “Managing Interim and Year-End Closing,” Processing an Undo Close, page 389.

See Also

Chapter 17, “Managing Interim and Year-End Closing,” Running the Close ApplicationEngine Process (GLPCLOSE), page 386

Chapter 17, “Managing Interim and Year-End Closing,” Defining Closing Rules, page 376


Interpreting the Results of Interim ClosingInterim closing sums all transactions that affect the selected P/L accounts and closes them toretained earnings. The system creates journal entries to update ledgers.

The system also creates offsetting entries. You can create offsets with alternative ChartFields. Ifyou offset to an account other than the source transaction, the audit trail remains intact. If theoffset account is the same as the source account, you close the account and no audit trail existsfor the closed accounts. The following examples illustrate this.

Create Offset Transaction

This table illustrates creating offsets with alternative chart keys.

P/L Balance410000

Retained Earnings Offset360101

Retained Earnings360100

100 CREDIT 100 DEBIT 100 CREDIT

Note. When you use an offset for interim close, it must be the target for the subsequent year-end close.



Close Account

This table illustrates creating offsets with the same account as the source document by selecting the Retain allCF Value for Offset (retain all ChartField value for offset ) option on the Net Income/Retained Earnings page:

P/L Balance410000



100 CREDIT

100 DEBIT

100 CREDIT

Performing Year-End ClosingThis section provides an overview of year-end closing and discusses how to:

• Complete a year-end procedures checklist.

• Perform year-end closing procedures.

• Interpret results of year-end closing.

• Define the relationship of interim close to year-end close.

Understanding Year-End ClosingsBefore year-end close begins, the process uncloses the periods in the fiscal year that is processed.It then closes the P/L accounts to retained earnings (storing them in period 999) and generatesthe balance forward amounts (storing these balances in period 0). It directly updates theledger and creates offsets to the retained earnings amounts.

Completing a Year-End Procedures ChecklistBecause final adjustments may not be known for weeks after year-end, closing a year and openinga new one is often an iterative process. PeopleSoft General Ledger enables you to carry on normalaccounting and reporting activities during year-end, while maintaining control over the closingprocess. The following procedures are typical of most year-end activities.

To complete the year-end process:

1. Run revaluation (if you manage financial information in multiple currencies).

2. Stop processing accounting transactions for the old year.

As you would at the end of any accounting period, use the Open Period Update page or OpenPeriods Mass Update page to change the range of open fiscal years and accounting periods toprohibit the entry and posting of additional transactions to the old year.

3. Produce preliminary year-end reports.

Produce the usual period-end reports and any other special year-end reports.



4. Begin to process the new year.

As you do at other times of year, you can use the Open Period Update page or Open Periods MassUpdate page to open the first accounting period in the new year for entry and posting.

5. Record adjustments to the old year.

When you are ready to post adjusting entries to the old year:

• Enter them as adjusting journals.

• Alternatively, reopen the appropriate accounting period, enter and post theentries, and close the period again.

6. Close the old year.

To close revenue and expense accounts to retained earnings and roll forward beginning balances tothe new year, use the Close Request page to initiate the background request. PeopleSoft GeneralLedger performs closing according to the options selected in the closing rules.

7. Produce reports for the new year.

Until you run year-end closing, reports for the next year do not include any results fromprior years. Once you run the close process, balance sheet accounts and inception-to-daterevenue and expense accounts are available for reporting.

8. Make additional adjustments to the old year.

When you need to make additional adjustments for the old year, follow the same processthat you use to record adjustments to the old year.

9. Reclose the old year.

Whenever you make adjustments to a closed year, you need to run year-end closing again to ensurethat the opening balances for the new year reflect all activity for prior years.

Performing Year-End Closing ProceduresYear-end closing involves three major tasks.

To perform a year-end close:

1. Define ChartField value sets.

If you plan to close to multiple retained earnings accounts, you need to define the sets of values forthe ChartFields that the system uses as the source for the year-end closing. These can be the samesets of ChartFields that you use for interim closing or different value sets.

Specifically, you need to create ChartField value sets for the ChartFields to be closed to retainedearnings. (You define ChartField value sets on the ChartField Value Set page.)

2. Define closing rules.

Define the rules for the year-end close. Specifically, you need to identify:

• Which P/L accounts are closed to the various retained earnings accounts.

• Whether to store P/L reversal entries.

• Whether to have beginning balances reflect separate debits or credits, or whetherto reflect the net of the debits and credits.



• Whether to close the general ledger periods.

• Whether to create journal entries for the year-end entries.

• Which ChartField value sets to use for the roll-forward amounts.

3. Run the closing request.

When you request that the year-end close be processed, you identify:

• Which ledger to close.

• Which closing rule to use.

• Which date to use as the closing date.

• Which business units to close.

In addition, note the following points:

• If you perform interim closes using an offset to retained earnings, you must perform allinterim closes for all the interim periods and use the offset account defined for the interimcloses as the target retained earnings for the year-end close.

• You run year-end close using the Close Request page.

• You can undo a close, if necessary, using the undo procedure.

See Also


Chapter 17, “Managing Interim and Year-End Closing,” Selecting Closing Rules Closing Options, page 377

Chapter 17, “Managing Interim and Year-End Closing,” Creating the Close Request , page 386

Chapter 17, “Managing Interim and Year-End Closing,” Processing an Undo Close, page 389

Interpreting Year-End Closing ResultsThe process of year-end closing closes the profit and loss (P/L) accounts to retained earnings and generates thebalance forward amounts. To maintain the integrity of financial reporting, the entries generated by year-endclosing are stored in special system-defined periods. The year-end closing entry to book the current year netincome to retained earnings is stored in period 999, and the balance forward amounts are stored in period 0.

The following example illustrates how PeopleSoft General Ledger stores amounts in a ledgerafter closing has been performed for the old year (998 is an adjustment period). This ledger usesa simplified calendar containing only four accounting periods.



Storing amounts in a ledger after closing

Note. The PeopleSoft General Ledger financial statement reports do not include beginningbalances for profit and loss accounts.

See Also


Defining the Relationship of Interim Close to Year-End CloseOnce you have determined to use interim close, it should be performed consistently for thedaily, monthly, or quarterly period chosen. If at any time you do an ad hoc interim close,you should subsequently perform an undo of that close.

If you do not use an offset to the retained earnings account when performing interim closes, the P/L accountsare closed and the balance is transferred to the retained earnings account as shown in the following example:

P/L Balance410000



100 CREDIT

100 DEBIT

100 CREDIT

When the interim closes are performed consistently, the P/L accounts is correctly closed at year-end andthe correct amount is recorded in the applicable retained earnings account. Completing the year-endclose then involves closing any remaining unclosed P/L accounts to retained earnings.



If you use an offset to the retained earnings account when performing interim closes, theoffset must be defined as the target for the year-end close. All P/L accounts must be closedto the offset account rather than to the retained earnings.

This is because when using an offset account for interim close, the P/L accounts retain theirbalances—they are not zeroed out during interim close. The following example shows the resultsof an interim close in which account 360101 offsets the amount in the revenue account 410000 andthe revenue is correctly reflected in the retained earnings account 360100.

P/L Balance410000



100 CREDIT 100 DEBIT 100 CREDIT

When the final interim close is performed, the year-end closed must be performed with theP/L accounts closed to the offset account 360101.

Defining Closing RulesTo define closing rules, you use the Closing Rules component.

This section provides an overview of closing rules and discusses how to:

• Select closing rules closing options.

• Specify net income and retained earnings ChartField values.

• Specify journal options.

• Specify roll-forward options.

Understanding Closing RulesClosing rules define how PeopleSoft General Ledger calculates retained earnings and carries forwardbalances to the new year. The PeopleSoft system provides flexibility in the determination of howretained earnings are calculated. Depending on your needs, you can:

• Close all profit and loss accounts to a single retained earnings account in total for a business unit.

• Close all profit and loss accounts to a single retained earnings account, but break down this amount by theDepartment ChartField, the Project ChartField, or any other ChartField that you select to track profit and loss.

• Close selected profit and loss accounts and ChartFields to multiple retained earnings accounts.

• Close by selected book code using accounts with a particular book code, or close tooverridable accounts and retain the book code.

You can define any number of closing rules for different contingencies.



Pages Used to Define Closing Rules


Closing Options CLOSE_DEFN1 General Ledger, CloseLedgers, Closing Rules,Closing Options

Identify the type of closing(interim or year-end),closing scope, and otherclosing options.

Net Income/RetainedEarnings

CLOSE_DEFN2 General Ledger, CloseLedgers, Closing Rules, NetIncome/Retained Earnings

Identify the P/L ChartFieldvalue sets and the retainedearnings ChartFields for theclosing.

Journal Options CLOSE_JOURNAL General Ledger, CloseLedgers, Closing Rules,Journal Options

Define journal options forsystem-generated journalscreated during the close.Also, specify whether tocreate journal entries foryear-end close.

Roll Forward Options CLOSE_DEFN3 General Ledger, CloseLedgers, Closing Rules, RollForward Options

For year-end close only,identify whether to rollforward accounts with 0balances. Also, indicatewhether to roll forward none,some, or all of the profit andloss accounts. (Normallyonly balance sheet accountsare rolled forward.)

Selecting Closing Rules Closing OptionsAccess the Closing Options page.

Interim Closing Rules - Closing Options page



Year End Closing Rules - Closing Options page

Description Enter a brief description of the closing rule to appear on pages and reports.

Ledger Template Select the ledger template associated with the ledger to be closed.

The system uses this template to determine which ChartFields to list in theselection fields for the closing rule. Only the ChartFields defined for theselected ledger template can be included in the closing rules.

When you select a ledger group on the Close Request page, the ledger groupmust be associated with the ledger template entered here.

Scope For interim closings only, enter the scope of the interim close. Values are:

Incremental Current Period:Includes current period balance (fromperiod start date to the end of period date).

Incremental Year to Date:Used for daily close, includes transactions thatyou have posted since the last closing process, up to the as-of date enteredon the Close Request page. The closing process marks the journals that itprocesses asClosed,and the journals are not processed in future runs.

Incremental Year to Curr Period(incremental year to currentperiod): Includes transactions starting with period 1 (that is, period1 through the end of the current period).

Target Currency Option For Interim closings, identify which base currency is used for theclosing journal entries and offsets. Values are:

Base currency of Prim Ledger(base currency of primary ledger):Uses the base currency of the primary ledger in the ledger group(as entered on the Detail Ledger Group page). The ledger group isautomatically entered on the Close Request page.

Business Unit Base Currency:Uses the base currency of the business unit.

Retain currency:Uses the source transactions’ currency.

Specify Target Currency:Uses the currency that you specify inthe Target Currency field.

To retain the offset entry in the original currency, select the Currency CodeChartField on the Journal Options page, and select Retain Value.

Target Currency If you selectSpecify Target Currencyin the Target Currency Optionfield, enter the currency for the system-generated closing journals. Be



sure that it is a base currency for one of the ledgers in the ledger groupthat you select on the Close Request page.

Be careful when you enter a target currency. Because you have not yetidentified the ledger group that is processed for the closing, the systemcannot validate that the currency is valid for the ledger group.

Adj Periods Included(adjustment periodsincluded)

Select the adjustment period that the system closes in the interim closing.Click the Add button to close additional adjustment periods. (Adjustmentperiods are defined on the Defining Detail Calendars page.)

Year End Closing Options Select to access the year-end close options. The link is availableonly for year-end closings.

Click the Year End Closing Options link.

Year End Close Options page

Close by You can perform year-end close on either the Account ChartFieldor the Alternate Account ChartField.

In addition, you can define a year-end closing rule on the Alternate Account)only. In this case, no Account ChartField is required for retained earnings,P/L ChartField value sets, or roll-forward ChartField value sets. Closingpopulates the Account ChartField with the default values for the particularAlternate Account ChartField. However, you can enter an Account ChartFieldto accompany the Alternate Account ChartField if you want.

To perform a year-end close by Alternate Account ChartField only,selectALTACCTin the Close by field.

In the close sequence, you typically perform a currency translation fromthe local ledger to a reporting ledger. You then close and report the localledger by Alternate Account ChartField. You can then close and reportthe translated reporting ledger by the Account ChartField.

Set Default RetainedEarnings

Select to use the default retained earnings that you also defineon the Closing Options page.



If not selected, you must use the Net Income/Retained Earnings page todefineall accounts to be closed. If you do not select this check box, nodefault retained earnings account exists for P/L accounts that may haveinadvertently been omitted on the Net Income/Retained Earnings page.

When you use the balance sheet indicator option at the installation level,this option is set toOff, and it is display-only.

Create Jrnl by RE Group(create journal by retainedearnings group)

Select to have year-end close create separate journals for each P/LChartField value set group and retained earnings pair; that is, one journalfor one ChartField value group number. For example, to have a separatejournal for each department, you might enterDEPTID in the ChartFieldvalue set criteria, as well as in the retained earnings ChartFields on NetIncome/Retained Earnings page and then select this option.

Close the G/L OpenPeriods (close the generalledger open periods)

Select to close all open general ledger periods for thebusiness-unit-and-ledger-group combination and year being closed. Thisprevents any additional journals being entered for the year that is being closed.

Store P/L Reversal Entries(store profit and loss reversalentries)

Select to store P/L offsets in period 999 (where the closing entriesfor all accounts are stored). .

If you select this option, the system inserts ledger rows for the entries madeto period 999 to close revenue and expense accounts. You can access theseamounts using the PeopleSoft General Ledger inquiry pages.

If this option is not selected, offsets are not stored in period 999. If youselect period 999 for reports, the ledger will be out of balance.

Initialize DR/CR with NetBal (initialize debit/creditwith net balance)

Select to begin the year with net balances of debits and credits, instead ofcarrying forward separate balances for debits and credits.

This option is available only if you have enabled separate debit/credit(DR/CR) on the database. When separate DR/CR is enabled, the period999 entries for P/L accounts offset not only the net ending balances,but also the debit and credit ending balances.

If selected, the debit or credit balances are initialized withthe net period 0 balance.

If not selected, the system moves the ending debit balance and ending creditbalance forward to become the beginning balances of the following year.

Specifying Net Income and Retained Earnings ChartField ValuesAccess the Net Income/Retained Earnings page.



Net Income/Retained Earnings page

Close To Multiple RetEarnings (close to multipleretained earnings)

Select to close to multiple retained earnings accounts.

If cleared (year-end closings only), the system uses the default account forretained earnings defined on the Closing Options page. All P/L accountswill close to the default retained earnings account.

This option is required when Book Code option, the Balance Sheet option,or the Off-Balance Sheet option is selected at installation.

Closing Offset Options Use for interim close only. Options are:

• Autofill Offset From First Row: Copies from the offset defined in thefirst row down to any offsets that are not yet populated.

• Fill Individual OffsetVerifies whether an offset is entered forevery ChartField group.

• Retain All CF Value for OffsetCloses to the same date and same detailaccount as the source transaction. If not selected, specify the ChartFieldand value for the offset using the fields in the Offset Chartfields groupbox. If you select this option, no audit trail exists.

Note. This option is available for interim closings only.

Retain Earnings Define the mapping of P/L accounts to retained earnings accounts.



ChartField Value GroupNumber

Each Chartfield Value Group comprises a group of P/L ChartField value setsto close to a single retained earnings account. To close to multiple retainedearnings, click the Add button to create additional ChartField value groups.

Profit/Loss Identify the P/L accounts (source accounts) to be closed.

Chartfield Value Set Select the ChartField value set for the P/L accounts to be closed. If there areother P/L ChartField value sets that close to the same retained earningsaccount, click the Add button and select the appropriate ChartField value set.

The system uses the values in these ChartField value sets to identifythe P/L accounts that close to the retained earnings account that youenter in the Retained Earnings group box.

For best system performance, select ChartField value sets that have thesame ChartField combinations. For example, if you select ChartFieldvalue sets 1, 2, and 3, and ChartField value set 1 includes the DepartmentChartField and the Project ChartField, then the other ChartField valuesets should also include Department and Project. If they includeddifferent ChartFields (for example Product and Project), then processingthe close may take longer and be less efficient.

Update/New Click to access the Setup ChartField Value Sets page where you can createor update a ChartField value set to use as P/L ChartField value set.

Retained Earnings Identify the retained earnings account (target account) to whichthe P/L accounts are closed.

ChartField Select a ChartField. The default is the Account ChartField, which is therequired ChartField, unless you have changed the name of the AccountChartField. (If you have modified your ChartFields, be sure to change theAccount field on the Ledger Template – Field Definitions page.)

You can select additional ChartFields, such as Department or Product.Click the Add button to add ChartFields.

Retain Value Select to retain the ChartField value from the original journal entry.

If the check box is cleared, you need to specify a value in ChartField Value field.

This option in not available for the Account ChartField.

ChartField Value Select the specific retained earnings account. This option isrequired for the Account ChartField.

If you perform interim closes using an offset to retained earnings, you mustuse the offset account as the target retained earnings for the year-end close.

For other ChartFields, if you have not selected Retain Value checkbox, enter a specific ChartField value here.

Offset Chartfields For interim closings only, identify the ChartField and ChartField valuefor the offset to the retained earnings entries.

If the Retain all CF Value for Offset check box is selected, thefollowing fields should be left blank.



ChartField For interim closings only, this can be only the Account ChartField, orit can be a combination of ChartFields (for example, Department andAccount.) If the Retain all CF Value for Offset check box is cleared,Account is required and must be the first ChartField entered.

Select a ChartField for a contra-equity offset. To offset to a combination ofChartFields, click the Add button to select additional ChartFields.

Retain Value Select to retain the ChartField value from the original journal entry.

If the check box is cleared, specify a value in the ChartField Value field.

ChartField Value If you do not select the Retain Value check box, enter a specificChartField value here.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining and Using ChartFields,”Defining and Using Account Types and Attributes

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining and Using ChartFields,”Using the Balance Sheet Indicator and Book Code

Chapter 17, “Managing Interim and Year-End Closing,” Single Versus Multiple RetainedEarnings Account Closings, page 366


Specifying Journal OptionsAccess the Journal Options page.

Journal Options page

Journal ID Mask Enter a prefix for naming closing journals. Journals are identified bya 10-character alphanumeric ID. The system automatically appendsthe prefix that you specify here to the journal IDs. For example, ifyou specify the journal ID mask asYEC,the year-end closing journalIDs might be YEC0001, YEC0002, and so on.



Alternatively, the valueNEXTcauses the system to assign the next availablejournal ID number automatically, without include the mask. (This optionmakes it more difficult to identify the closing journals.)

Reserve a unique mask value for closing to ensure that no otherprocess creates identical journal IDs.

Source Enter a code to identify the origin of the journal entries that are created.

Closing Doc Type(closingdocument type)

If you use the Document Sequencing feature, select a predefined closingdocument type for the closing journals. The Document Sequencing featurerequires that you identify a document type for all created journal entries.

Description Enter a description of the journals that are created (for example,Daily Close Journals).

Closing Journal DateOption

Values are:

Retain Transaction Date:Sets the output journal date to equalthe original transaction date.

Use Process Date:Sets the output journal date to equal the processdate of the closing process run.

Create Journal Entries Select to create journal entries for year-end close transactions only.Interim close always creates journal entries.

The following three fields are for interim close only (because year-end close directly updates the ledgers andinterim close does not). If you select these fields, the system processes the journals without any interventionby you. If you want to edit and post the journals through journal processing, do not select the fields.

Edit Journal(s) For interim close only, select to have the journals automaticallyundergo the edit process.

If you do not select this option, the closing process designates thejournals asNo Status - Needs to be Edited.

Budget Check Journal(s) For interim closings only, select to have the journals automatically checkedagainst the Commitment Control budget for the business unit and account.

To select this option, you must have the Commitment Control feature enabledfor the ledger group, and you must have selected the Edit Journal(s) option.

Post Journal(s) For interim closing only, select to have the journals automaticallyposted to the ledger.

To select this option, you must have selected the Edit Journal(s)option and the Budget Check Journal(s) option if the CommitmentControl feature is enabled for the ledger.



See Also

Chapter 17, “Managing Interim and Year-End Closing,” Interpreting theResults of Interim Closing, page 371

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Setting UpBasic Commitment Control Options”


Specifying Roll-Forward OptionsAccess the Roll Forward Options page.

Roll Forward Options page for year-end close

Note. These fields appear for year-end closings only. They are not available for interim closings.

Do Not Roll Forward ZeroBal (do not roll forwardzero balances)

Prevents the system from creating balance-forward amounts (period0) for accounts with a 0 ending balance.

P/L to Roll Forward toNext Yr (profit and loss toroll forward to next year)

Normally, only balance sheet accounts are rolled forward, and their balanceforward amounts stored in period 0. Options are:

• Do Not Roll Forward

• Partial RollForward 1 Year

• Partial RollForward Cumulative

• Roll Forwrd All 1 Year

• Roll Forward All Cumulative

Roll Forward Profit/Loss If you elect to roll forward in the P/L to Roll Forward to Next Yr field,select the ChartField value set for the P/L accounts that you want to roll



forward. To roll forward more than one ChartField value set, click theAdd button and select additional ChartField value sets.

Update/New Click to access the Setup ChartField Value Sets page, where you can create orupdate a ChartField value set to use as the roll-forward P/L ChartField value set.

Running the Close Application Engine Process (GLPCLOSE)You use similar procedures to run the Close process for an interim closings and a year-endclosings. Both procedures use the Close Request page.


• Create the close request.

• Monitor validation checking.

Pages Used to Run the Close Application EngineProcess (GLPCLOSE)


Close Request CLOSE_REQUEST General Ledger, CloseLedgers, Request LedgerClose, Ledger Close Request

Specify the process requestparameters to perform aninterim or year-end close forone or more business units.

Creating the Close RequestAccess the Ledger Close Request page.



Ledger Close Request page

Request Number Displays the system-generated number used to order a series of requests.

Close Request Type Specify the type of close that the system runs. Options areCloseandUndo.

In case of an error, to reverse the retained earnings (interim or year-endclosings) and balance-forward calculations (year-end closings), selectUndo.

For year-end close, it is not necessary to undo a close before rerunningthe close because existing amounts are deleted first.

Closing Type If you selectUndo in the Close Request Type field, the ClosingType field becomes available. Select the type of closing to undo.Options areYear Endand Interim.

Previous Close to Undo To display the Previous Close to Undo group box, selectUndo forthe close request type and selectInterim for the closing type. Selectthe process instance and business unit for the close thatyou want toundo. If you want to undo more than one close, click the Add buttonto enter another process instance and business unit.

Note. Obtain the process instance from the process log.

Fiscal Year Enter the year to be closed or the year of the closing that you wantto undo if you selectedYear Endas the closing type.

Business Unit forPrompting

Select a business unit to determine which ledger groups and closing rules canbe selected. Only ledger groups and closing rules associated with the businessunit are available for selection in the Ledger Grp and Closing Rule fields.



Check only, Do not process Select to have the Close process perform validation checking but notcalculate retained earnings or balance-forward amounts.

Closing Rule Select the closing rule to use for this request.

Ledger Group Select the ledger group for the ledger being closed.

Ledger Leave blank if the Keep Ledgers in Sync option is enabled forthe selected ledger group selected.

If the Keep Ledgers in Sync option is not enabled for the ledger group,you can either enter a specific ledger to process or leave this fieldblank to process all ledgers in the ledger group.

BU Process Date(businessunit process date)

Select this option to use the process date of the business unit as theas-of date for the closing process. This is recommended if you aresubmitting a group of interrelated requests for processing (for example,journal posting, revaluation, and interim close).

As of Date Enter a specific date for the closing process.

Selections Select the business units to close or use trees to identify whichbusiness units to close.

Selected Detail Values Select to enter one or more business unit values in the BusinessUnit to Close field.

Detail - Selected Parents Specify a tree containing the business units that you want to close. All businessunits for the tree setID, tree and level (if applicable) are included in the close.

Tree SetID, Level,andTree If the Detail - Selected Parents option is enabled, select a tree setID, tree, andlevel (if applicable) for the group of business units that you want to close.

Business Unit to Close If the Selected Detail Values option is enabled, select a business unit in theSelect Value field. To close or undo a close for more than one businessunit, click the Add button and select another business unit.

The business unit must be associated with the ledger groupthat you entered previously.

See Also

Chapter 17, “Managing Interim and Year-End Closing,” Processing an Undo Close, page 389

PeopleTools PeopleBooks: PeopleSoft Process Scheduler, "Understanding PeopleSoft Process Scheduler"

Monitoring Validation CheckingDuring closing, PeopleSoft General Ledger performs validation checking for the business unit and closingrule. Specifically, the system determines whether the following conditions exist:

• All ChartFields in the closing rule are valid for the business unit and ledger.

• All ChartField values are valid.

• All retained earnings accounts are valid for the business unit.



• Any duplication or overlapping in the P/L selection criteria occurred.

(This condition could cause double entries to retained earnings accounts.)

The system displays an error message if any of these validations fail.

Processing an Undo CloseIf you need to reverse the retained earnings (interim and year-end closing) and balance-forwardcalculations (year-end closing), you can run an undo process.

Note. For year-end close, it is not necessary to run an undo close before rerunning a year-endclose because existing amounts are always deleted first.

The undo process differs depending on whether you undo an interim close or a year-end close.


• Undo an interim close.

• Undo a year-end close.

Undoing an Interim CloseWhen you run the interim close process, the system creates an entry in the process log that includes:

• User ID.

• Closing rule.

• As-of date.

• Date-time stamp.

• Source instance (which comprises process instance and request number).

To undo an interim close:

1. Obtain the process instance and business unit from the process log.

2. Enter the process instance and business unit on the Close Request process page.

The system calls the Journal Posting process to unpost or delete the journals, whichever is necessary.

Undoing a Year-End CloseTo undo a year-end close, enter the ledger group, ledger (if necessary), fiscal year, andbusiness units that you want to unclose.

When you run an undo for a year-end close and you elect not to create journal entries, the system clears theperiod 999 (results of year-end close) and period 0 (balance-forward) rows from the ledger. To create journalentries, the system deletes the journal entries and clears the period 999 and period 0 rows.



Producing Interim and Year-End Closing ReportsThis section lists the standard closing reports. Running a report entails selecting it from a menu and enteringany necessary parameters. Once you enter the report parameters, use Process Scheduler to run the report.

This section discusses how to generate the Journal Closing Status report.

Pages Used to Produce Interim and Year-End Closing Reports


Closing Rules report RUN_GLS1002 General Ledger, CloseLedgers, Closing RuleReport

Specify run parameters forthe Closing Rules report(GLS1002 SQR)

The report lists detailedinformation about theclosing set rules.

Closing Trial Balance RUN_GLS1003 General Ledger, CloseLedgers, Closing TrialBalance

Specify run parameters forthe Closing Trial Balancereport

The GLS1003 SQR reportlists summary informationof all entries on the ledgerby account type.

The report shows the ledgerentry account type with itsbeginning balance andperiod total, along with anyadjustments made to thebeginning balance. It alsolists the closing entry andperiod total amounts forthe year.

Journal Closing StatusReport

RUN_GLS1004 General Ledger, CloseLedgers, Journal ClosingStatus Report

Specify the run parametersfor the Journal ClosingStatus report.

Generating the Journal Closing Status ReportAccess the Journal Closing Status Report page.



Journal Closing Status Report page

Note. This page is discussed in detail because it involves more parameters than thesystem usually requires for generating reports.

Display Full Numeric Field Select to display the full numeric value if it is larger than the reportcolumn size. The number wraps to a second line.

Select From Closing LogTable

Select to have the scope of the report defined by the process instance stored inthe closing log table. The Process Instance field becomes available.

Process Instance Enter the process instance number of the Close process run.

Report Closing Status Select one of the following:

All: Includes all journals regardless of their closing status.

All Except: Includes only journals that the Close process processed.

Closed:Includes only journals that the Close process (GLPCLOSE) closed.

Not ProcessIncludes only journals that the Close process did not process.

UnclosedIncludes only journals that the Close process processedbut did not close.

ChartField Selection Enter a sequence number and ChartField field long name. Use the Selectoption to include only selected values, and enter a value.

Note. To modify standard reports, create your own reports, or reformat report output, you canuse a variety of reporting tools that the PeopleSoft system provides.

See Also

PeopleTools PeopleBooks: PeopleSoft Reporting Tools




CHAPTER 18

Reviewing Financial Information

This chapter provides an overview of the resources to review PeopleSoft General Ledger’sfinancial information and discusses how to:

• View journal information.

• View ledger information.

• Inquire about ledger groups.

• Configure ledger summary and detail inquiries.

• Compare data by ledger periods.

• Compare across ledgers.

• Review imported accounting entries.

• Review entry event accounting.

Note. This chapter does not include Commitment Control inquiries.

See Also


Understanding Ledger, Journal, and FinancialInformation Inquiries

PeopleSoft General Ledger provides a series of inquiries that enable you to review ledger summaryand detail ledger information based on selected ChartField combinations. These inquiries useseveral successive views that take you down to journal line details. The ledger inquiry also enablesyou to drill down across products from account balances in PeopleSoft General Ledger to specifictransaction entries in other PeopleSoft Financials and Distribution products.

These terms are used in this chapter:

Regular Balance View a regular balance when you inquire on the balance of a ledger and you donot include any adjustment entries, balance forward entries, or closing entries.This balance only includes transactions posted during the specified period.

Cumulative Balance View a cumulative ledger balance when you inquire on the balanceof a ledger by including balance forward entries, adjustment entries


Reviewing Financial Information Chapter 18

and closing entries. Each balance is added to the next balance toprovide a cumulative ledger balance.

Base Amount The transaction amount converted to the base currency indicatedfor the transactions business unit.

Posted Total Base Amount The total ledger amount expressed in the base currency.

Transaction Amount The amount of the transaction entered in a currency that is different fromthe base currency or is the same currency as the base currency.

Posted Total TransactionAmount

Amounts in the transaction currency for all ledger balancesincluding those in the base currency.

Posted Total Amount Total amount of the transactions in the transaction currency for allledger balances except those in the base currency.

Note. Many of the following inquiry pages operate in deferred processing mode. Most fields are not updatedor validated until you save the page or refresh it by clicking a button, link, or tab. This delayed processinghas various implications for the field values on the page—for example, if a field contains a default value,any value you enter before the system updates the page overrides the default. Another implication is that thesystem updates quantity balances or totals only when you save or otherwise refresh the page.

See Also


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Editing ChartField Combinations”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Using TimeSpans

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Using Journal Generator,”Convert Accounting Entries to PeopleSoft Journals

Inquiry OverviewThese inquiries are accessible in PeopleSoft General Ledger:

• Journal Inquiry

Enables you to review a specific journal or multiple journals within a ledger for a business unit and accountingperiod. You can use a document sequence number as part of your search criteria to review journal data.

• Ledger Inquiry

Select a ledger to view based on selected ChartField values, including book codes, or ChartField value sets,which consist of a predefined set of selection criteria for a given ChartField . A ChartField value setcan be obtained from a tree, a series of detail ChartField ranges of a series of detail ChartField values.There are also various methods for displaying both summary and detail ledger information.

• Ledger Group Inquiry


Chapter 18 Reviewing Financial Information

Review all the journals within a ledger group along with their journal line details. Compare the postedtransaction amount, posted base amount, or posted total amount balances between ledger periods.

• Ledger Comparisons

Compare one ledger by periods or compare one ledger with another within one or more ledger periods.Customize your comparison by selecting specific ChartFields or ChartField value sets. You can displaycomparisons for all thirteen periods or for selected periods, with or without adjustments.

• Analytic Charts

Display analytic bar charts of the comparison across ledgers amounts.

• Imported Accounting Entries Inquiries

Import PeopleSoft Payroll, Student Financial, and Enterprise Learning Management transactions,as well as generic accounting line data into PeopleSoft General Ledger and review thisimported data before and after you run Journal Generator.

• Entry Event Budget and GL Adjustment Accounting Inquiries

Drill down to the accounting line detail for Budget and GL adjustment transactions that use entry events.

Viewing Journal InformationIn this section we discuss how to:

• Enter journal criteria.

• View journal header details.

Pages Used to Review Journal Information


Journal Inquiry - JournalInquiry Criteria

INQ_JRNL_CRITERIA General Ledger, ReviewFinancial Information,Journals, Journal Inquiry -Journal Inquiry Criteria

Review summary and detailjournal information for aspecific business unit,ledger, and period.

Journal Inquiry - JournalInquiry Details page

INQ_JRNL_HDR_DTL After displaying the journals,click a Journals link.

Displays the journal’sheader, currency, and lineinformation.

Entering Journal CriteriaEnter all or some of the information at the top of the Journal Inquiry Criteria - Journal Inquiry page andclick the Search button to display the Journals based on your selected criteria.



Journal Inquiry − Journal Criteria page

Document SequenceNumber

Enter the document sequence number or click the Search buttonto select a number. This enables you to review journals that aretracked by a document sequencing number.

Journal ID (journalidentification)

Click a Journal ID link to review the journal header and line detail information.

Note. You can use Customize to hide or display specific journal column data.

Viewing Journal Header DetailsAccess the Journal Inquiry Details - Journal Inquiry page.



Journal Inquiry - Journal Inquiry Details page

Show All Linesor Show,From Line: Thru Line:

Display all the journal lines for this journal, or enter a range of linenumbers and select Query Journal Lines.

Journal Line - Line # Click a journal line number to view the journal transaction’s details.This is only available for a subsystem journal.

See Also

Chapter 8, “Making General Ledger Journal Entries,” page 107


Viewing Ledger InformationIn this section we discuss how to:

• Specify ledger criteria to review summary and detail information.

• View ledger summary balances.

• View ledger transaction details.

• View detail journal header and journal lines.



• Drill down to the subsystem accounting entries.

• View the ledger details.

Pages Used to Review Ledger Information


Ledger Inquiry - LedgerInquiry Criteria

INQUIRY_CRITERIA General Ledger, ReviewFinancial Information,Ledger.

Click the Ledger Balanceslink to access the LedgerBalances page.

Click the Ledger Activitylink to access the LedgerActivity page.

Ledger Activity

Specify selection criteria toview detail and summaryledger information.

Ledger Inquiry -Summarization Details

INQ_SUM_BAL Click one of these links toaccess the Ledger Inquiry -Summarization Details.

Balances by Account

Balances by Acct, Dept(balances by account,department)

Balances by Acct, Project(balances by account,project)

Sum by Period, Account

Sum by Period, Account,Dept (department)

Sum by Period, Alt. Acct.(alternate account)

Sum by Period, Project

Displays the ledger’ssummary balances based onselected criteria.

Ledger Inquiry - TransactionDetails

INQ_TRANS_DETAIL Click the Activity linkon the Ledger Inquiry -Summarization Details pageto access this page.

Displays the summary ofthe ledger’s journal dataon your selection. Forexample, a summary of allthe ledger’s journal amountsfor a specific accountChartField value.

Journal Inquiry - JournalInquiry Details

INQ_JRNL_HDR_DTL Click the Journal ID of one ofthe transactions.

Displays the journaltransaction’s headerinformation and journallines.

Accounting Entry XX_ACCT_ENTRY_JRNL Click the Journal Linenumber.

Displays the subsystemjournal’ accounting entries.



Page Name Object Name Navigation UsageLedger Inquiry - LedgerBalances

INQ_DETAIL_LEDGER Click the Details linkon the Ledger Inquiry -Summarization Details page.

Displays the ledger detailsfor a selected period. Selectthe Activity link on this pageto return to the LedgerInquiry - Transaction Detailspage and drill down to thesubsystem level of detail.

Specifying Ledger Criteria to Review Summaryand Detail InformationAccess the Ledger Inquiry - Ledger Inquiry Criteria page.

Ledger Inquiry − Ledger Inquiry Criteria page

Ledger Criteria

You can enter or select the following fields to establish ledger criteria.

Unit Select the ledger criteria fields based on the ledger data you want to review.

Currency Use the % wildcard to simplify your search for the field value.

Stat (Statistics Code) Use the % wildcard to simplify your search for the field value.

Include Balance Forward Select this option to include any balances that were broughtforward into the current open year.



Include Closing Select this option to include closing balances (period 999) alongwith the current open period amounts.


Select this option to include any adjustment period amounts. If you selectthis option a range of adjustment period fields appear:

Adjustment Period From and To

998 displays in both fields because it is the adjustment periodused by PeopleSoft.

Only in Base Currency Select this option if you want the inquiry amounts to appear only in thebase currency indicated for the selected business unit.

Max Rows (maximum rows) You can override the default of100with any number <=200 rows ofdata that you can display in a scroll area.

Search Click to display the following active and inactive links listed underView and the ChartField Criteria group box.

View

You can select one of the following methods to display information based on your ledger criteria.

Per Balances by Account Select Include Balance Forwardand then select Per Balances byAccount to display posted transaction and balance amounts fora period by activity and account.

Per Balances by Acct, Dept(per balances by account,department)

Select Include Balance Forwardand then select Per Balances by Acct,Dept to display posted transaction and balance amounts for periodby activity, account, and department. .

Per Balances by Acct, Prj(per balances by account,project)

Select Include Balance Forwardand then select Per Balances byAcct, Prjto display posted transaction and balance amounts forperiod by activity, account, and project.

Sum by Period, Account Select to display the Summarization Details — Ledger Inquiry page, whichcontains summarized posted transaction amounts by period and account.

Sum by Period, Account,Dept (sum by period,account, department)

Select to display Inquiry - Summarization Details page, which containssummarized posted transaction amounts by period, account, and department.

Sum by Period, Alt Acct(sum by period, alternateaccount)

Select to display the Ledger Inquiry - Summarization Details page,which contains a summarized of posted transaction amounts byperiod, activity, and alternate account.

Sum by Period, Project Select to display the Ledger Inquiry - Summarization Details page, whichcontains summarized posted transaction amounts by period and project.

Ledger Balances Select to display the Ledger Inquiry - Ledger Balances page, whichcontains the ledger balances based on the ChartFields selected inthe ChartField Criteria group box.

Ledger Activity Select to display the Ledger Inquiry - Transaction Details page, which containsjournal lines based on the selected ledger criteria and ChartField criteria.



Clear Criteria Clears the Ledger and ChartField Criteria from the page andenables you to enter different criteria.

Delete Criteria Deletes the inquiry, cancels the page, and returns you to a blankLedger Inquiry - Ledger Inquiry Criteria page.

ChartField Criteria

You can select one or more ChartField values or leave the fields blank and place a check mark nextto each row to review all ChartField information based on the selected criteria.

ChartField/Value Lists all the ChartFields set up for the selected ledger. Select a ChartFieldvalue for one or more ChartFields to review specific data in a ledgeror use a wildcard (%) to select a range of values.

ChartField Value Set Select a predefined set of selection criteria for a given ChartField.

Update/New Select this option to update an existing ChartField Value Set’s dataor create a new ChartField Value Set.

View If you selected Ledger Balances or Ledger Activity, select the ChartFieldsthat you want to display in either of these inquiries.

See Also


Viewing Ledger Summary BalancesClick one of the links to access the Summarization Details - Ledger Inquiry page.



Summarization Details - Ledger Inquiry page

Ledger Amount byCurrency

Displays, based on type of currency, a summary of the transaction balances foreach account in the ledger within the selected ledger period range.

Activity Click to view the Transaction Details on the Ledger Inquiry- Transaction Details page.

Detail Click to view the Ledger Details on the Ledger Balances - Ledger Inquiry page.

Viewing Ledger Transaction DetailsOn the Summarization Details - Ledger Inquiry page click Activity to access the TransactionDetails on the Ledger Activity - Ledger Inquiry page.



Ledger Inquiry - Transaction Details page

Journal ID Click this link to access the Journal Inquiry - Journal Inquiry Details page.

Viewing Detail Journal Header and Journal LinesOn the Ledger Activity - Ledger Inquiry page click a Journal ID to access the JournalInquiry Details - Journal Inquiry page.

Journal Inquiry Details - Journal Inquiry page



Journal Line Click the line number to drill down to the transaction’s associatedsubsystem’s (Billing) accounting Entry page.

Drilling Down to the Subsystem Accounting EntriesClick the Journal Line number link to access a subsystem’s Accounting Entry page.

Accounting Entry page.

GL Journal general ledgerjournal

Click this link to access the Journal Lines page that contains all of thejournal lines that comprise this journal. You can click on each Journal Linenumber on this page to access the details on the journal line.

Viewing the Ledger DetailsReturn to the Ledger Inquiry - Summarization Details page and click Detail to accessthe Ledger Balances - Ledger Inquiry page.

Ledger Balances — Ledger Inquiry (1 of 2)



Ledger Balances — Ledger Inquiry (2 of 2)

Activity Click this link to return to Transaction Detail on the Ledger Activity - LedgerInquiry page. There you can again view each of the pages listed above untilyou reach the subsystem’s accounting entry drill down page.

Inquiring About Ledger GroupsIn this section we discuss how to:

• Review ledger group information.

• View journal lines.



Journals Inquiry INQ_JRNL_HEADER General Ledger, ReviewFinancial Information,Ledger Group, Journals

Inquire on the journalscontained in the ledgers ofa ledger group.

Journal Lines Inquiry INQ_JRNL_LINE Click the Drill to JournalLine button.

Displays the journal lines ofeach journal in the ledgergroup.

Reviewing Ledger Group InformationAccess the Journals page:



Ledger Group − Journals Inquiry page

Journals Criteria Enter the criteria to access one or more journals in a selected ledger group.

Search Click this button to display the journal header detail for each journal containedwithin the ledger group after entering the search criteria.

Show All Select to show all journal lines associated with this ledger groupwhen you click Drill to Journal Line button.

From Line andThroughLine

Enter the specific journal line numbers that you want to display whenyou click Drill to Journal Line button.

Currency Details If you enabled the Separate DR/CR Amount Fields on the Ledgers for aUnit – Definition page for a detail ledger, the amounts for the currencyin the primary ledger display in DR and CR fields, as well as the Netamount of the two. If Separate DR/CR is not enabled, amounts displayas a negative for a credit and a positive for a debit.

Viewing Journal LinesAccess the Journal Lines Inquiry page.



Journals- Journal Line Inquiry page

Query Journal Line Again If you queried to display a specific number of journal lines to reviewon this page, you can enter one or more different journal line numbersand select this option to display them along with the journal linesthat you displayed with your original query.

Configuring Ledger Summary and Detail InquiriesYou can control which ledger summary and detail inquiry links display in the Showoptions area of the Ledger Criteria page.

In this section we discuss how to:

• Add summary inquiry options.

• Add detail inquiry options.



Summary Options INQ_REC_PANEL General Ledger, ReviewFinancial Information,Define Inquiry Record andPanels, Summary Options

Controls the ledger summarylinks that display underShow in the Ledger Criteriapage.

Detail Options INQ_REC_PANEL Click Detail Options tab. Contains the recordsassociated with the detailledger inquiries on theLedger Criteria page.



Adding Summary Inquiry OptionsEnter a Ledger Template to access the Summary Options page.

Inquiry Records and Pages page—Summary Options tab

Adding Summary Inquiry Options

To add a new summary inquiry, follow these steps:

1. Clone the records using the following rules:

a. The Summary Inquiry, Level 1 Record must contain these fields: BUSINESS_UNIT,LEDGER, CURRENCY_CD, STATISTICS_CODE, BASE_CURRENCY, FISCAL_YEAR,POSTED_TOTAL_AMT, and POSTED_BASE_AMT. INQ_SUM_TOTALS (level1 record for template STANDARD) and INQ_SUM_TOT_BD (level 1 record fortemplate BUDGETS) contain all these required fields.

b. The Summary Inquiry, Level 2 Record must contain the following fields: BUSINESS_UNIT,LEDGER, CURRENCY_CD, STATISTICS_CODE, BASE_CURRENCY, FISCAL_YEAR,ACCOUNTING_PERIOD, POSTED_TOTAL_AMT, POSTED_BASE_AMT, DISP_TEXT.If this is a summary inquiry that displays cumulative balances, these three fields are requiredas well: DISP_TEXT2, LEFT_BALANCE, RIGHT_BALANCE.

2. The Detail Inquiry Record should contain BUSINESS_UNIT, LEDGER, FISCAL_YEAR,ACCOUNTING_PERIOD, CURRENCY_CD, STATISTICS_CODE, BASE_CURRENCY,POSTED_TOTAL_AMT, POSTED_BASE_AMT, DISP_TEXT, and all your ChartFields.

3. You can click the Add a new row button or click the Delete a row button.

4. You must select a Level 1 Record and a Level 2 Record for each option you add.

5. Enter a description, which displays as a link to these records.

6. Select the Show Cumulative Balances check box if this is cumulative balance inquiry.

Note. You probably only need to clone the Summary Inquiry Level 2 Record. In our delivered samples,all the Summary Inquiry Level 1 Records are the same, as are the Detail Inquiry Records.

Adding Detail Inquiry OptionsClick on the Detail Options tab to access the page.



Inquiry Records and Pages page—Detail Options tab

Adding Detail Inquiry Options

To add a new detail inquiry option, follow these steps:

1. You can click the Add a new row button or click the Delete a row button.

2. Select a detail Record.

3. The Long Description field determines the order in which data is displayed in your page.

Comparing Data by Ledger PeriodsYou can select and compare ChartFields of a selected ledger entries based on selected accounting periods.


• Enter search criteria.

• Compare ledger by period.



Pages Used to Compare Data by Ledger Period


Ledger Period Comparison -Ledger Selection Criteria

INQ_LED_CMP_PNL General Ledger, ReviewFinancial Information,Ledger Period Comparison,Ledger Selection Criteria -Ledger Period Comparison

Specify the ledger data youwant to compare by period.

Ledger Period Comparison -Period Comparison Results

INQ_LEDCOMPARE_PNL Select Search on the LedgerSelection Criteria page.

Displays a comparison ofthe selected ledger’s detailbased on the ChartFields andnumber of periods selectedon the Ledger Criteria page.

Display ChartField Criteria -ChartField Criteria

INQ_LED_CMP_DTL Click the ChartFieldCriteria Link on the PeriodComparison Results page.

Enables you to select orunselect various ChartFieldvalues to display.

Entering Search CriteriaAccess the Ledger Period Comparison - Ledger Selection Criteria page.



Ledger Period Comparison - Ledger Selection Criteria page

Amount to Display Select POSTED_TRAN_AMT to display the amounts in the transactioncurrency for all ledger balances including those in the base currency.

Select POSTED_BASE_AMT to display the total of the transactionamounts converted to the base currency of the ledger.

Select the POSTED_TOTAL_AMT to display the amounts in the transactioncurrency for all ledger balances except those in the base currency.

Include All Periods Includes all thirteen periods if selected.

Include Balance Forward Includes any balances carried forward from the previous period in the totals.

Include Closing Includes closing adjustments for period 999 in the totals.

ChartField Criteria Use this group box to select the ChartFields and ChartField values that youwant to appear on the Ledger Compare Detail page. To limit the number ofChartField values, enter a specific Value for a selected ChartField. You can also



use a wildcard % to select a range of values. If you do not specify ChartFieldvalues, the system determines the values to use based on the selected ledger.

The Alternate Account ChartField (AltAcct) appears in the ChartFieldCriteria group box only if you enabled the alternate account option on theInstallation Options−Products page and the Ledgers for a Unit page.

Period Selection Use this group box to select the periods you want to use for comparisonon the Ledger Compare Detail page(s). To remove a period from thelist, select the Delete check box for the row and click the Delete button.Select the adjustment periods you want to display.

Search Click this link to access the Ledger Compare Detail page(s).

Comparing a Ledger by PeriodAccess the Ledger Comparison page.

Ledger Period Comparison — Ledger Period Results page (1 of 2)



Ledger Period Comparison — Ledger Period Results page (2 of 2)

Period Bal Fwd (periodbalance forward)

If you selected the Include Balance Forward option, this column appearson the first tab and displays the opening balance for the period.

Period Close If you selected the Include Closing Adjustments option, this column for period999 appears on the last tab. It displays the adjustment for year-end closing.

ChartField Selection If you click this link, it displays the list of ChartFields. Clear or select eachChartField check box. ChartField and click Refresh. The Ledger Comparisonpage redisplays with the columns of ChartFields based on your selections.

Comparing Across LedgersYou can select and compare total amounts of selected ChartField criteria between two ledgers.


• Enter comparison criteria for two ledgers.

• Review comparison amounts between the ledgers by period.

• Use a bar chart to analyze the ledger comparison data.



Pages Used to Compare Ledgers Across Periods


Compare Across Ledgers -Compare Across LedgersCriteria

INQ_COMPARE_PNL General Ledger, ReviewFinancial Information,Compare Across Ledgers

Specify the criteria for thethat you want to compare.

Compare Across Ledgers -Compare Ledgers - Data

INQ_COMPARE_PNL Click Search Displays the ledgercomparison data.

Compare Across Ledgers- Compare Ledgers -Bar Chart

INQ_COMPARE_PNL SelectAmount,selectDisplay Chart in theCompare Across LedgersCriteria page and selectSearch.

Displays a bar chart ofthe data.

Entering Comparison Criteria for Two LedgersAccess the Compare Ledgers page.

Compare Across Ledgers − Compare Ledgers page



Compare Ledgers Enter the criteria for the two ledgers you want to compare and save thepage. The Grid appears in which you can select specific ChartFields andcriteria that you want to be included in your comparison.

Amount/Percentage Select whether you want the variance between the ledgers to displayas an amount or a percentage in the comparison information. If youselectAmount, the Display Chart field appears.

Display Chart Select to display an analytical chart. If you selectedAmountin the previousfield, when you select Search, you can scroll down to view a bar chartbelow the comparison data that shows a comparison between the amountsin Ledger 1 and Ledger 2 along with the variance between the two.

Search Click to display the comparison detail information when you use the scrollbar to scroll down below the selection criteria information.

Sum By This option is only applicable to ChartFields that are common to both ledgers.

Value Required Indicate the ChartFields you want to contain values.

Order By When you select the Sum By check box for a ChartField, it automaticallydisplays a number that determines the order in which the inquiryresults are retrieved and displayed.

Book Code You can generate an inquiry which includes Book Code ChartField values.Book Code must be set as active on the PS_ACCT_ATTRIB_TBL for itto display as ChartField selection criteria on this page.

Reviewing Comparison Amounts Between The Ledgers by PeriodDepending how you set up your criteria, the two selected ledgers are compared toone another for each ledger period.

Scroll down to the comparison information.



Compare Across Ledgers − Results page

Variance May appear as an amount or a percentage depending on which fieldvalue you select for the Amount/Percentage field.

Note. This page is also integrated with the CFO Portal.

Using a Chart to Analyze the Ledger Comparison DataAccess the Compare Ledgers page and scroll down to the chart.



Compare Ledgers — Ledger Comparison by Period Bar Chart

Reviewing Imported Accounting EntriesYou can inquire about PeopleSoft Payroll, Generic, Student Financial, and Contributor Relationsaccounting lines that you import into General Ledger.

In this section we discuss how to inquire on imported accounting entries.

See Also




Pages Used to Inquire on Accounting Lines


Payroll Accounting Entries -Payroll Acctg

PY_DRILL_PNL General Ledger, ReviewFinancial Information,Payroll Accounting Entries

Inquire on accounting linesthat have been importedinto General Ledger fromPeopleSoft Payroll.

Enterprise LearningManagement Acctg − ELMAcctg (ELM accounting)

ELM_JRNL_DRILL General Ledger, ReviewFinancial Information,Enterprise LearningManagement Acctg, ELMAcctg

Inquire journals importedfrom Enterprise LearningManagement (ELM) toGeneral Ledger.

Generic Accounting Entries- Gen Acct Ent

JGEN_ACCTG_DRILL General Ledger, ReviewFinancial Information,Generic Accounting Entries

Inquire on genericaccounting entries inGeneral Ledger. Theseaccounting lines includeentries that you import intoPeopleSoft General Ledgerusing the Journal Generatorprocess (FS_JGEN).

Student Fin AccountingEntries

SF_DRILL_PNL General Ledger, ReviewFinancial Information,Student Fin AccountingEntries

Review Learning Solution’simported student financialaccounting entries.

Contributor Relations Acctg.AV_DRILL_PNL General Ledger, ReviewFinancial Information,Contributor Relations Acctg.

Review Learning Solution’simported contributorrelations accounting entries.

Inquiring on Imported Accounting EntriesBefore you can use any of these inquiry options, you must:

• Import payroll accounting lines into PeopleSoft General Ledger.

• Import ELM accounting lines into PeopleSoft General Ledger.

• Import generic accounting entries into PeopleSoft General Ledger.

• Import student financial accounting entries into PeopleSoft General Ledger.

• Import contributor relations accounting entries into People

Note. You use the same method to access the accounting entries for all of these Review Ledger/Journal options.

To access accounting entries that were imported to General Ledger:

1. Enter the Business Unit, Journal ID, Journal Date, GL Journal Line number, and Ledger.

The Payroll, Generic, ELM, Student Financial, or Contributor Relations accountingjournal information appear at the top of the page.

2. Review the accounting entry data that appears in the lower portion of the page.

3. There are four pages of data concerning the selected Journal ID:



• ChartFields

• More ChartFields

• Currency Details

• Misc.

Reviewing Entry Event AccountingIn this section we discuss how to:

• Drill down to entry event budget accounting details.

• Drill down to entry event GL adjustment accounting details.

Pages Used to Review Entry Event Accounting


Entry Event BudgetAccounting Entries

EE_BUD_DRILL General Ledger, ReviewFinancial Information, EntryEvent Budget Acctg, EntryEvent Budget AccountingEntries

Drill down to budgetaccounting entry eventtransaction details.

Journal Header JOURNAL_HEADER_FS Click Go to GL Journal link. Displays Journal Headerinformation for the EntryEvent GL Adjustmenttransaction.

Journal Lines JOURNAL_LN_FS Select Journal Lines tab Displays Journal Line detailfor the Entry Event GLAdjustment transaction.

Entry Event GL AdjustmentAccounting Entries

EE_GLADJ_DRILL General Ledger, ReviewFinancial Information, EntryEvent GL Adjust Acctg,EE Adjust Drill

Drill down to GL adjustmentaccounting entry eventtransaction details.

Drilling Down to Entry Event Budget Accounting DetailsAccess the Entry Event Budget Accounting Details page.



Entry Event Budget Accounting Entries

Account Displays the account(s) generated by the Entry Event processorthat are posted to the budget.

GL Journal (go to generalledger journal)

Click to review the Journal Header and Journal Lines page for this transaction.

Drilling Down to the Entry Event GL AdjustmentAccounting DetailsAccess the Entry Event GL Adjustment Accounting Entries page.

Entry Event GL Adjustment Accounting Entries page

Account Displays an entry event accounting line generated by the Entry Event Processor.

GL Journal (generalledger journal)

Click to access Journal Header and Journal Lines page for this transaction.


CHAPTER 19

Maintaining Standard Budgets in PeopleSoftGeneral Ledger

This chapter provides an overview of PeopleSoft General Ledger standard budgets and discusses how to:

• Maintain detail budgets.

• Maintain project budgets.

• Copy budgets.

• Import budgets from spreadsheets.

• Post budget journals.

Understanding PeopleSoft General Ledger Standard BudgetsPeopleSoft General Ledger enables you to develop, maintain, and report on standard budgets,also referred to as static budgets. As with actual or statistical data, you maintain budgets in aledger. You can create any number of separate ledgers to track various types of budgets, includinghigh-level forecasts and budgets based on summary ChartField levels.


• Methods for creating and maintaining standard budgets.

• Budget spreading, repeating, and percentage-increase processes.

• Budget Copy process.

• Budget Allocation process.

Note. Standard budgets do not include control budgets, which are set up and maintainedusing the Commitment Control feature.

PrerequisitesBefore you enter amounts in a budget ledger, you must:

1. Define a ledger template.

2. Link the template to a detail budget ledger.

3. Add the budget ledger to a budget ledger group.

4. Activate the budget ledger groups for business units.


Maintaining Standard Budgets in PeopleSoft General Ledger Chapter 19

Note. The Scenario ChartField in the budget ledger and budget journal line records does not exist in thestandard ledger definition. PeopleSoft Budgeting uses the Scenario ChartField extensively because thatChartField facilitates an integration link between PeopleSoft Budgeting and PeopleSoft General Ledger. Evenif you do not currently use PeopleSoft Budgeting or populate values for this ChartField, retain the additionalChartField in the general ledger budget records. You cannot include a budget ledger in a budget ledger groupwith other types of ledgers. That is, you must not include budget ledgers with an actuals (recording) ledgeror any other type of ledger in a ledger group. You do not have to use the same accounting calendar fora budget that you use for an actuals (recording) ledger. You create calendars on the Detail Calendar page,activate the budget ledger, and select the calendars that you want to use for the standard budgets.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Defining a Ledger Template

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Defining a Ledger Group




PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining and Using ChartFields,” Adding Scenario Values

Methods for Creating and Maintaining Standard BudgetsYou can set up standard budgets based on fixed amounts or percentages. In addition,you can set up standard budgets by:

• Copying amounts from other ledgers.

• Cloning existing budgets or loading data from spreadsheets.

• Using automatic replication and spreading.

• Creating an unlimited number of budget versions.

• Configuring budget worksheets with PS/nVision.

You can also set up standard budgets that:

• Budget at any level in the organization.

• Budget for any period of time.

• Reflect potential organizational changes in budget reports without affecting current financial reports.

You can use PeopleSoft Tree Manager to do this.


Chapter 19 Maintaining Standard Budgets in PeopleSoft General Ledger

Note. PeopleSoft General Ledger integrates with PeopleSoft Budgeting, which shares all of thefunctionality described in this section. If you use PeopleSoft Budgeting to manage the budget processand prepare budget ledger data, you have immediate access to that budget data for reporting andcomparison with PeopleSoft General Ledger actuals data. Many of the steps described in this sectionapply only if youdo notuse PeopleSoft Budgeting for budget preparation.

SeePeopleSoft Enterprise Performance Management PeopleBook: “PeopleSoft Budgeting”

Typically, you maintain budgets in anunbalancedledger. With expense budgets and sales forecasts, forexample, you are normally concerned with only one side of the accounting equation. Because you use mostbudgets for planning and analysis (and you continually modify and round them), you may not need to createan exact offset every time that you change a budgeted amount. The Detail Budget Maintenance pages thatenable you to modify budget rows directly are supported only against unbalanced ledgers.

In PeopleSoft General Ledger, you can:

• Enter and modify budget amounts by sets of ChartFields or by period.

• Enter a lump sum to be spread across multiple periods for a ChartField combination.

• Copy any combination of ledger rows from existing ledgers.

• Import budgets from spreadsheets.

• Allocate amounts to a budget ledger.

• Enter budget journals.

Except when entering allocations and budget journals, you update the ledger balances tabledirectly with no audit trail. By entering journals and posting them to the budget ledger orselecting the Request Allocations option to create journals in allocations, you maintain thesame audit trail as with actuals (recording) transactions.

• Create an all-encompassing and detailed budget by cloning the actuals ledger, and then you cangenerate a budget summary ledger to maintain higher-level information.

• Create a budget using an across-the-board percentage, such as a payroll increase based on a 4.5 percentcost-of-living index or a sales target forecast that is 10 percent higher the following year.

Simply copy the amounts from the actuals ledger and have PeopleSoft General Ledgerautomatically adjust those amounts by the specified percentage.

• Spread a given amount (for example, 15 million USD budgeted for equipment) evenly across specificChartFields or according to a basis (such as the statistics code for employee headcount).

• Adjust budget amounts for each individual ChartField combination by period.

Budget Spreading, Repeating, and Percentage-Increase ProcessesThe budget spreading and repeating processes provide an alternative to the often time-consuming job ofspecifying budget amounts on an amount-by-amount, period-by-period basis. You can enter a lump sumbudget amount or a percentage of an existing amount for a ChartField combination.

PeopleSoft General Ledger can automatically spread an amount or apply a percentage acrossthe periods in a fiscal year. The amounts can be:



• Added by period.

• Repeated by period.

• Spread evenly across the periods.

You can also use percentage changes by period.

Spreading or repeating a fixed amount or percentage over a range of periods reduces data entry. Hereis an example. Suppose that you send a memo to the manager of the Account Management departmentindicating that the monthly office party expense for January through June will be 1,200.00 USD. Themanager repeats the 1,200.00 USD amount for each month during that period.

When you review the Sales department’s budget, however, you realize that you have made a mistake, and yousend another memo clarifying that 1,200.00 USD is the entire amount for the half-year period, and it must bedivided evenly among the six months. The manager decides to spread a negative 6,000.00 USD evenly acrossthe January through June time period. This leaves 200.00 USD in each monthly period and corrects the error.

Now suppose that after you consider the number of new employees, you decide to add 200.00 USD toeach monthly period for a total expense of 2,400.00 USD. However, before the budget is finalized, youreceive a memo from the budget committee directing you to reduce all nonessential sales and all general andadministrative expenses by 50 percent. After you reduce the selected monthly expenses by the required50 percent, you have 1200.00 USD for the final office party budget for the six months period.

This table shows the transactions:

JAN FEB MAR APR MAY JUN

Repeat1200,00USD

1200 1200 1200 1200 1200 1200

Spreadevenly6000.00USD

-1000 -1000 -1000 -1000 -1000 -1000

Balance 200 200 200 200 200 200

Add byperiod200.00 USD

+200 +200 +200 +200 +200 +200

Balance 400 400 400 400 400 400

Percentagechange byperiod

-50% -50% -50% -50% -50% -50%

Balance 200 200 200 200 200 200



Remember the following points when you spread amounts:

• You cannotspread amounts to closed periods.

• You cannotspread amounts to balanced ledgers or to summary ledgers.

• You can spread positive or negative amounts.

Budget Copy ProcessThe Budget Copy feature is ideal for creating multiple versions of a budget. You set up what-if scenariosor assess the impact of each level of review. You can use this feature to create a new budget based onan existing ledger, or to update an existing budget and have PeopleSoft General Ledger automaticallyincrease or decrease the amounts copied by a percentage that you specify.

The Budget Copy process updates or inserts new rows of data into the selected target ledger. If datafor the specified ChartField values in the pool (source) ledger already exists in the target ledger, thesystem updates (or overwrites) that data for the year and periods specified. If no data exists in thetarget ledger for the specified ChartFields, PeopleSoft General Ledger adds those rows to the targetledger. Any rows that do not meet the pool ledger criteria remain unaffected.

Here is an example. Suppose that the sales manager for corporate headquarters expects that the revenue forthe eastern and central regions will increase by 128 percent in the year 2000. To create a sales projectionfor the year 2000, the manager copies the actuals amounts from 1999 to the budget ledger. From theactuals ledger, the manager selects a range of revenue accounts (400000-401000) and the appropriate salesdepartments (21200 and 21300). All products and services are included. The system copies only thoseaccount balances that match the ChartField values that the manager entered. Any other rows of data thatalready exist in the budgets ledgers are not affected. Next, the manager selects the appropriate value inthe Factor % (factor percentage) field. In this case, it is 128 percent of the actuals balances.

To populate a year’s worth of budgets with a one-to-one copy from the actuals ledger to the budgetsledger, you set up a period-to-period copy. Then you run it 12 times in the Budget Copy processrequest using a different as-of date for each request. You cannot use a multiperiod time span (suchasAll Year) in the pool definition because the Budget Copy process sums the entire year in onerow rather than as period 1, period 2, and so on. You could spread that amount to one period at atime or over an entire year, but you would not perform a one-to-one copy.

Budget Allocation ProcessAllocations processing in PeopleSoft General Ledger enables you to spread either fixed amounts or a poolof complexpro rata amounts from multiple ChartFields. You can use statistical and monetary accountsfrom any ledger (or combination of ledgers) as the basis. Allocations provide complete flexibility inmapping ledger amounts across the chart of accounts; you can use allocations to generate large volumes ofbudget entries quickly and easily. Allocations processing supports top-down budgeting and the dynamicgeneration of budgets based on any segment of the organization at any given time.

Allocations enable you to spread amounts from any ledger to the budget ledger so that you can devise budgetsand forecasts based on the strategic information already stored in your database. Here is an example. Supposethat your sales manager is preparing next year’s monthly sales targets for the eastern sales division, as wellas a budget for travel expenses. The sales manager bases the forecast on a number of factors:

• 2004 revenue should be 128 percent higher than 2003 amounts.



• Because of unusual market fluctuations in 2003, the manager wants the 2004 forecastto reflect the 2002 monthly sales trends.

• The travel expense budget will be 10 percent higher than last year, allocated usingthe new sales projections as a basis.

First, the sales manager uses the Budget Copy Definition pages to copy 2002 eastern sales regionrevenue figures from the actuals ledger into the budget ledger for 2004.

The manager uses the Factor (%) field to increase by 128 percent the 1998 actuals amounts. Then thesales manager does the same for the travel expense accounts, increasing them by 10 percent.

Next, the sales manager uses the Budget Allocation process to reallocate revenue amounts according to 2002sales trends, using the 2002 amounts in the sales revenue account for all departments as the basis. In this way,sales figures for the eastern division are spread according to the general sales trends for 2002.

As the final step, the sales manager uses the new 2003 sales revenue forecast amountsas the basis for allocating the travel expenses.

See Also

Chapter 19, “Maintaining Standard Budgets in PeopleSoft General Ledger,”Maintaining Detail Budgets, page 426

Chapter 19, “Maintaining Standard Budgets in PeopleSoft General Ledger,” Copying Budgets, page 432

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Processing Allocations”

Maintaining Detail BudgetsYou use the Detail Budget Maintenance page, the Data by Year page, and the Data by Period page to makeadjustments and perform inquiries on budget ledgers. To access budget ledger data using these pages, theledger definition must specify the ledger record as LEDGER_BUDG, and the ledger must be unbalanced.


• Select budget ChartField criteria.

• Adjust budget data by year.

• Adjust budget data by period.

• Use the Budget Calculator feature.

Note. To maintain transactions in different currencies, use allocations or budget journalsrather than the Budgets pages described here.



Pages Used to Maintain Detail Budgets


Detail Budget Maintenance BE_ENTRY2 General Ledger, MaintainStandard Budgets, DetailBudget Maintenance

Identify the fiscal year andthe ChartFields or specificChartField values thatappear on the Data byYear page and the Data byPeriod page for the selectedbusiness unit and budgetledger.

Data by Year BE_ENTRY3A Click the Query link on theDetail Budget Maintenancepage.

Delete rows for the selectedbudget data and enteredfiscal year and drill down tothe Data by Period page forthis specific account.

Data by Period BE_ENTRY4 Click the Account link on theData by Year page.

Delete or add rows andmaintain budget detailinformation by period.

Selecting Budget ChartField CriteriaAccess the Detail Budget Maintenance page.

Detail Budget Maintenance page

To use the Detail Budget Maintenance page:



1. Enter the fiscal year that you want to review or modify for the business unit and budget ledger.

2. Enter or select ChartField values.

You can use wildcard characters to narrow your search of ChartFields.

3. Click the Query link at the bottom of the page.

The Data by Year page displays the data for each selected ChartField for the specified year.

Adjusting Budget Data by YearAccess the Data by Year page.

Data by Year page (1 of 2)



Data by Year page (2 of 1)

To use the Data by Year page:

1. Select the Del/Cal (delete/calculate) check box next to the ChartField rows that you want to eitherrecalculate (by clicking the Calculate link) or delete (by clicking the Delete button).

2. To view the Data by Period page and adjust information for an account on a period-by-periodbasis, click the account value link in the Account field for a specific row.

3. To return to the ChartFields page, click the ChartFields link.

Note. You can enter data for ledgers only if the Ledgers For A Unit - Definition pagespecifies direct budget ledger updates.

See Chapter 19, “Maintaining Standard Budgets in PeopleSoft General Ledger,” Usingthe Budget Calculator Feature, page 430.

See Also


Adjusting Budget Data by PeriodAccess the Data by Period page.



Data by Period page (1sof2)

Data by Period (2 of 2)

To use the Data by Period page:

1. Modify values, add or delete selected rows of data, or perform calculations on specified periods.

2. Select the Calculator link to access the Budget Calculation page, where you can modifybudget calculations for accounts by period.

Using the Budget Calculator FeatureClick the Calculator link on either the Data by Year page or the Data by Period pageto access the Budget Calculation page.



Budget Calculation page

Calculation Type Select to determine how the system spreads the amount acrossthe specified periods.

Repeat Amount by Period Select to replace the amount in each successive period with the change value.

Spread Evenly by Period Select to divide the amount by the number of periods, distributingit evenly to each period.

Percent Change Select to designate a percentage by which the system increasesthe amount each period.

Add by Period Select to designate a specific amount to add to each period.

Selected From PeriodandSelected to Period

Select the period range for which to apply the change.

Note. These fields appear only when you select the Calculatelink on Data by Period page.

Change Value Enter the change value amount based on the selected budgetperiod (either a year or a period).

For example, suppose that you enter 12,000.00 USD to spread evenlyover 12 periods, replacing the original budget of 60,000.00 USD, and youselect OK on the Budget Calculation page. On the Date by Period page,no value appears in the Current field, and 12,000.00 USD appears in theRevised amount field. The Change field indicates the reduction in the periodamounts from 5,000.00 USD to 1,000.00 USD, and the % Change fielddisplays a negative 80.00 as the overall percentage reduction.

Note. If the percentage of change is more than 99999.99 percent, it appears as99999.99%

Maintaining Project BudgetsThis section discusses how to review and modify project budgets.



Pages Used to Maintain Project Budgets


Detail Project Maintenance BD_P_ENTRY2 General Ledger, MaintainStandard Budgets, DetailProject Maintenance

Select the fiscal year and theChartField values to appearon the Data by Year page.

Data by Year BD_P_ENTRY3A Click the Query link on theDetail Project Maintenancepage.

View the budget data forall projects that exist in theselected budget ledger forthe selected fiscal year.

Data by Period BD_P_ENTRY4 Click the account numberlink on the Data by Yearpage.

View the project budgetdata for selected projectsfor each period within theselected fiscal year.

Reviewing and Modifying Project BudgetsYou maintain project budgets the same way that you maintain standard budgets. Project budgetsnormally include project detail information, which you can modify.

See Also

PeopleSoft Project Costing 8.8 PeopleBook, “Budgeting Project Costs and Planning Revenue”

Chapter 19, “Maintaining Standard Budgets in PeopleSoft General Ledger,”Maintaining Detail Budgets, page 426

Copying BudgetsTo copy budgets, use the Budget Copy Definition component (ALLOC_COPY_LEDGER) andthe Budget Copy Group component (ALLOC_GROUP_BD).


• Set up the budget copy definition pool.

• Set up the budget copy definition target.

• Create a budget copy group.

• Initiate budget copy processing.



Pages Used to Copy Budgets


Budget Copy Definition- Pool

ALLOC_POOL_BD General Ledger, MaintainStandard Budgets, BudgetCopy Definition, Pool

Specify the pool records,the selection criteria, andthe method for the copy.Copy or update an entireledger or any combinationof ChartField values froma source ledger to anunbalanced ledger within thesame business unit. Onceyou set up the pages in theBudget Copy Definitioncomponent, you save andreuse them.

Budget Copy Definition -Target

ALLOC_TARGET_BD General Ledger, MaintainStandard Budgets, BudgetCopy Definition, Target

Specify the destination forthe copy of the target recordsand field values.

Budget Copy Records ALLOC_REC_BD_SEC Click the Records link on theBudget Copy Definition -Target page.

View the names of thecalculation log record andworking record for the targetledger.

Amount Map ALLOC_AMT_BD_SEC Click the Amount Maplink on the Budget CopyDefinition - Target page.

View the amount fields forthe target budget.

Budget Copy Group ALLOC_GROUP General Ledger, MaintainStandard Budgets, BudgetCopy Group

Create a budget copy group.Each budget copy definitionmust belong to a budget copygroup. A budget copy groupcan contain multiple budgetcopy definitions.

Request Copy Budget- Budget Copy UsingAllocations

ALLOC_REQUEST General Ledger, MaintainStandard Budgets, RequestBudget Copy

Runs the COPY_BUDGprocess and the allocationprocess.

Budget Copy CalculationLog

RUN_GLS6003 General Ledger, MaintainStandard Budgets, BudgetCopy Calculation Log

View detailed informationabout the Budget Copyprocess calculations for agiven process step.

Setting Up the Budget Copy Definition PoolAccess the Budget Copy Definition - Pool page.



Budget Copy Definition - Pool page

Pool Record Enter the source budget ledger to copy.

TimeSpan Specify the period (relative to the current fiscal year and accounting period)for which to retrieve the source records. Enter a single or multiperiod timespan to determine the accounting periods used for the copy.

Pool factor Enter the factor that the system uses to increase or decrease the amountscopied to the target ledger. You can enter positive or negative values. Forexample, to increase 1,000.00 USD to 1,100.00 USD (10 percent), enter10,oryou could decrease the amount by 10 percent by entering–10.

Pool Fields Select the field name that the system uses to select pool rows from thepool record for the copy. The pool record name is the same as the ledgerrecord name that is defined in the ledger template. If the pool recorduses a subrecord to define its ChartFields, the prompt table for the fieldname does not list these ChartFields. However, you can still enter theChartFields. When you save the budget copy definition, the system checksthe record to validate the field name that you enter.

How Specified Specify individual pool field values, use trees to select ChartField values fromspecified levels and nodes, or specify a range of field values.

Note. Use trees whenever possible to reduce maintenance whenChartField values change.



Selected Detail Values Select to use detail values. Use the Specify Value/Range of Values group boxto list pool field values, such as specific department or account values.

Selected Tree Nodes Select to activate the tree information fields. In the Tree Type field,selectDetail to enter a range of detail values for a node. SelectDynamicto include the range of detail values defined by a table in the database.Enter each tree node. The tree level is optional. If the tree has levels,you can limit prompting in this field to selected levels.

Range of Values Select to activate the From and To fields to enter the start and end pool fieldvalues. If you leave the From field blank, the system selects all pool field valuesthat are less than or equal to the value in the To field. Youcannotleave the Tofield blank. If the field is blank, the system uses the lowest possible value.

Setting Up the Budget Copy Definition TargetAccess the Budget Copy Definition - Target page.

Budget Copy Definition - Target page

Note. Once the copy or update is complete, you can review the results on the ledger inquiry pages, or youcan review and modify the new budget using the Detail Budget Maintenance component.

Ledger Specify the target ledger to update. The system populates the Specify FieldValues scroll area with the target ledger ChartFields. Changing the value in theLedger field causes the data in the target fields to be deleted as the new valuesare populated. To ensure a one-to-one copy, all ChartFields that are common



to both the target ledger and the pool ledger must appear in the Specify FieldValues scroll area, and the value in the Source field must bePool.

Table Output Option Select one of the following options:

Update Existing Amounts:If target rows already exist, update these rows withthe pool amounts. For example, suppose that a target budget ledger row foraccount 400000 and department ID 12000 has an existing amount of 1,500.00USD. The corresponding pool actuals ledger row contains 2,500.00 USD. Ifyou select the update option, the system adds the amount in the pool ledger tothe target ledger row, resulting in a target amount of 4,000.00 USD.

Replace Existing Amounts:Existing amounts are replaced. In the precedingexample, the amount in the target row becomes 2,500.00 USD.

Both options apply only if target rows that meet the pool criteriaalready exist. If no target rows exist, the system inserts themregardless of the option that you selected

TimeSpan Specify the output for accounting periods for the target.

Target TimeSpan Option If you select multiple periods in the TimeSpan field for the target, youmust specify one of the following options:

Repeat Target Each PeriodRepeats the entire target amount foreach period defined in the time span.

Divide Target Across PeriodsDivides the target amount by the number ofperiods defined in the TimeSpan field and distributes it equally to each period.

Records Click to access the Budget Copy Records page, where you can view thenames of the calculation log record and working record for the targetledger. Budgets has extra ChartFields, such as LEDGER_PROJ (for projectbudget) has BUSINESS_UNIT_PC, ACTIVITY_ID, RESOURCE_TYPE,ANALYSIS_TYPE, RESOURCE_CATEGORY, RESOURCE_SUB_CAT,BUDGET_PERIOD and SCENARIO LEDGER_BUDG (for standardbudget) has BUDGET_PERIOD and SCENARIO. This means thatit is very important to specify the correct records.

Amount Map Click to access the Amount Map page, which displays the amount fields forthe target budget. In most cases, you can accept the default values.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,” TimeSpans

Creating a Budget Copy GroupAccess the Budget Copy Group page.



Budget Copy Group page

Step Enter the name of a process step to determine the processing order

Continue Select this check box for a particular step to have the systemcontinue the copy even if the step fails.

Click the Copy Allocation Group button to make a copy of the group.

Click the Rename Allocation Group button to rename the copy group.

Click the Delete Allocation Group button to delete the copy group.

Initiating Budget Copy ProcessingAccess Request Budget Copy — Allocation Request page to specify the request parameters and run theAllocation process (FS_ALLC) to copy the budget. If you select the Start Step option, the system startsprocessing from the last failed step. The Start Step option appears only if the prior step fails.

Importing Budgets from SpreadsheetsBudget data in PeopleSoft General Ledger is stored in ledgers; therefore, you import budgets directly to theDetail Ledger table (PS_LEDGER_BUDG), which is delivered with PeopleSoft General Ledger.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Importing and Exporting Ledgers



Posting Budget JournalsAs with other journals, you can create and post budget journals to the ledger that is specified in the journalheader. Unlike the other budgeting methods, however, you do not directly update the ledger balancestable. Rather, the posting process updates the ledger table and retains the journal entry as an audit item.In this way, you generate an audit trail to record the original budget and subsequent changes.

See Also



CHAPTER 20

Archiving Ledgers and Journals

This chapter provides an overview of archiving and discusses how to:

• Archive and restore ledgers.

• Archive and restore journals.

Understanding ArchivingThis section discusses:

• Archival to a table or file.

• Retention days and archive date.

Some ledgers—for example, the average daily balance (ADB) daily ledger—can include millionsof transactions. Such volume can impede system performance. Archiving helps maintain thevolume of data at a manageable level to improve system performance.

Note. Only the ledger template types of ADB reporting ledger and standard general ledger aresupported in the archiving ledger functionality described in this chapter. A separate and distinctarchiving process is used to archive commitment control data.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook,“Archiving for Commitment Control”.

Archival to a Table or FileArchive ledgers and journals as often as you need either to a file or to a table.

When you archive to a file, the system stores the archived data in a flat file. The file is stored based onthe location that you enter in the ARC field for the PS Configuration table. The file name comprisesrecord (ledger or journal), business unit, ledger name, and date (archive date).

When you archive to a table, the system stores the archived records in the tables that you specifyin the Archive Record Names group box on the Ledger Template page.

Archiving to a file may not be as efficient as archiving to a table. Consider archiving to atable ratherthan archiving to afile when archiving is an essential part of batch processing.

The archive function has a corresponding restore function. Archiving data precludes processingtransactions against the archived periods. Be sure to restore archived ledgers or journalsbefore processing data within the archived periods.


Archiving Ledgers and Journals Chapter 20

Every time you archive or restore, the system creates an entry log. The log includes statistical informationas of the archive date (for example debit and credit amounts, record counts, and time period). Youcan view this log from the Archive Ledger Log or Archive Journal Log page.

These tables are archived in PeopleSoft General Ledger:

FROM TABLE TO TABLE

LEDGER LEDGER_ARC

LEDGER_ADB_MTD LED_ADB_MTD_ARC

LEDGER_ADB_QTD LED_ADB_QTD_ARC

LEDGER_ADB_YTD LED_ADB_YTD_ARC

LEDGER_ADB LEDGER_ADB_ARC

JRNL_HEADER JRNL_HEADER_ARC

JRNL_LN JRNL_LN_ARC

OPEN_ITEM_GL OPEN_ITM_GL_ARC

JRNL_CF_BAL_TBL JRNL_CF_BAL_ARC

JRNL_VAT JRNL_VAT_ARC

Retention Days and Archive DateThe archive process archives the ledger data from the first day of the fiscal year of the archive date to thearchive date. The archive process determines the archive date based on the following:

• Requested archive date, which is determined by the request date option or as-ofdate on the Ledger Archive page.

• Retention days as entered on the Ledger Archive page.

• Calendar used to store the ledger data, identified for the ledger on the Ledgers for a Unit page.

The archive date is derived from the requested archive date minus the number of retention days.If the archive date falls between the period beginning and ending dates, then the process resetsthe archive date to the period-end date of the prior period.

The following examples illustrate how the archive date is derived. In the first example,it is assumed that the ledger uses a daily calendar.

Using a Daily Calendar

In this example, the ledger uses a daily calendar.


Chapter 20 Archiving Ledgers and Journals

Request Date Option Date Retention Days Archive Date

System Date 06/10/2002 10 05/31/2002

Process Date 06/10/2002 5 06/05/2002

As of Date 12/31/2001 0 12/31/2001

Using a Monthly Calendar

In this example, the ledger uses a monthly calendar.

Request Date Option Date Retention Days Archive Date

System Date 06/10/2002 10 05/31/2002

Process Date 06/10/2002 5 05/31/2002 *

As of Date 12/31/2001 0 12/31/2001

* Because the request date minus the retention dates (06/05/2002) falls within the period begin and enddate, the process resets the archive date to the period end date of the prior period.

The archive process archives the data from the first day of the fiscal year of the archive date. The processdoesnot archive across fiscal years. For example, suppose that you want to archive all of ledger dataof a business and ledger for the 1980s. You need to set up 10 process requests in the run control, onefor each year. Each archive request uses end-of-year as the as-of date (12/31/2000).

See Also

PeopleTools PeopleBooks:PeopleSoft Process Scheduler: "Understanding PeopleSoft Process Scheduler"

Archiving and Restoring LedgersIf you calculate ADBs, you may have a large number of transactions that require frequent archiving—forexample, weekly or daily. With smaller numbers of transactions, you may only need to archive ledgers yearly.


• Archive a ledger.

• Restore archived ledger data.

• View the archive ledger log.



Pages Used to Archive and Restore Ledgers


Ledger Archive ADB_ARCH_REQ General Ledger, ArchivingTables, Archive Ledgers,Request Ledger Archive,Ledger Archive Request

Archive a ledger to a tableor a file, or restore anarchived ledge. This is anApplication Engine process(GL_ADB_ARCH).

Review Archived LedgerLog

ARCH_LEDGER_INQ General Ledger, ArchiveTables, Archive Ledgers,Review Archived LedgerLog

View the statistics ofarchived ledgers.

Archiving a LedgerAccess the Ledger Archive Request page.

Ledger Archive Request page

Unit Enter a business unit to archive the ledger only for a particular business unit.

Leave blank to archive a ledger for all the business unitsassociated with the ledger. The system creates one file for eachbusiness-unit-and-ledger combination.

Ledger Enter the ledger that you want to archive.

ADB Ledger Select if the ledger the you want to archive is an ADB ledger (thesourceADB ledger containing the daily balances).

Archive Option Select a request option. Values are:

Archive to File: Select to archive the ledger data to a file. The filename isthe ledger record name (LEDGER), business unit, ledger name, and archivedate. (For example, LEDGERUS001ACTUALS12-31-99)

Archive to Table:Select to archive the ledger data to the tableidentified in the Ledger Archive table or the ADB Ledger Archivetable on the Ledger Template page.

Restore:Select to restore archived data. Enter a date in the Restore As of field.

Req Date Optn (requestdate option)

Specify the date option for the archive request date. Values are:

Process Date:Select to use the process date of the business unit asthe request date for the archive process.



SYSDATE:Select to use the system date.

As-Of Date:Select to use the date that you specify in the As ofDate field. For example, if to archive last year’s data, you wouldenter December 31st of that year.

As Of Date If As Of Datewas selected in Req Date Option, an As of Date fieldappears in the Process Request Parameters group box. Enter a datein this field only if you want to update the as-of date for the selectedledger. Another As of Date field appears below theProcess Monitor linkand Run button. Use this As Of Date field to update the as-of datesglobally for requests that use the as-of date option.

Note. This option is not available if you selectRestorefor the archive option.

Retention Days Enter the number of retention days for the ledger data. The system uses thissetting with the request date option to determine the archive date.

Note. This option is not available if you selectRestorefor the archive option.


Select to archive adjustment periods. After selecting this check box,enter the beginning and ending adjustment periods in the Adjust fromAccounting Period and Adjust to Accounting Period fields.

Include ClosingAdjustments

Select to include the adjustments created by the year-end closingprocess (which are stored in period999).

See Also




Chapter 20, “Archiving Ledgers and Journals,” Retention Days and Archive Date, page 440

Restoring Archived Ledger DataAccess the Ledger Archive Request page.

Note. The same page is used for both archiving and restoring ledgers.

Specify the business unit and ledger that you want to restore (and the date that the ledgerwas archived). When you restore an archived ledger, the system restores the entire ledgerdata that was archived from an archive request.

Archive Option SelectRestoreto restore the archived data. The system restores all of theledger data that was archived from an archive request as of a specified date.



Req Date Option(requestdate option)

When you selectRestore, the valueAs of Dateautomatically appears inthis field for the restore process. This value comes from the log entrythat was created when the ledger was archived. (You can determinethis date by viewing the ledger archive log.)

Restore As of Enter the as-of date for the restoration. The date is based on the log entrythat the system creates upon archiving the ledger. (You can determinethis date by viewing the ledger archive log.)

Viewing the Archive Ledger LogAccess the Review Archived Ledger Log page.

Review Archived Ledger Log page

Unit Select the business unit whose archived ledgers you want to review.

Ledger To view a specific ledger, select the ledger here. To view all archivedledgers for the business unit, leave the field blank.

As of Date To view only ledgers that have been archived as of a certaindate, enter that date here.

ADB Ledger Select to view the archived ADB ledger (thesourceledger thatstores the daily balances).

Search Click to view selected archive log entries statistics.

Archive Log Entries and Statistics Grid

Ledger Displays the ledger that was archived.

Status Displays the status. Values areArchivedandRestored.

Archive Date Displays the date that the ledger was archived.

The archive process creates a log entry for each unique unit, ledger,status, and archive date combination.

Last Update Date/Time Displays the date of the last update.

For example, if you have archived a ledger, restored it, and then archivedit again using the same archive date, there would be two listings for theledger—one with the statusArchiveand one with the statusRestore.TheArchivestatus line would have a later update date and time. Consequently,the current status of the ledger would be archive.

Archived Rows Displays the number of rows that were archived in the ledger.



Total Debit Displays the total debit amount for the ledger.

Total Credit Displays the total credit amount for the ledger.

Archiving and Restoring JournalsYou can archive journal header, line, and all corresponding journal sibling datawhenever and as frequently as you wish.

You can also restore journals as needed. For example, you might need to restore archivedjournals when to rerun a report that includes those journals.

This section describes how to:

• Archive journals.

• Restore archived journals.

• View the archive journal log.

Pages Used to Archive and Restore Journals


Journal Archive Request JRNL_ARCH_REQ General Ledger, ArchivingTables, Archive Journals,Request Journal Archive,Journal Archive Request

Archive journals to atable or a file, or restorearchived journals. This is anApplication Engine process(GL_JRNL_ARCH).

Review Archived JournalLog

ARCH_JRNL_INQ General Ledger, ArchivingTables, Archive Journals,Review Archived JournalLog

Review the entries andstatistics for selectedarchived journals.

Archiving JournalsAccess the Journal Archive Request page.

Journal Archive Request page

Unit Enter a business unit to archive the journals for a particular business unit.

Leave blank to archive journals for all business units.



Ledger Group Enter a ledger group to archive the journals for a particular ledger group.

Leave blank to archive journals for all ledger groups.

Archive Option Enter a request option. Values are:

Archive to File: Select to archive the journal data to a file. The filenameconsists of the journal records (such as JRNL_HEADER and JRNL_LN),the business unit, the ledger group, and the archive date—for example,JRNL_HEADERUS001ACTUALS12-31-99.

Archive to Table:Select to archive the journal data to the tablesidentified on the Ledger Template page.

Restore:Select to restore archived data. Enter a date in the Restore As of field.

Request Date Option Specify the date option for the archive request date. Values are:

Process Date:Select to use the date as of when the process started.

SYSDATE:Select to use the system date.

As-Of Date:Select to use the date that you specify in the As of Date field.

If As Of Datewas selected in the Request Date Option group box, the As ofDate field and Update As Of Date icon appear with the Process MonitorRequest link and the Runbutton. Click the Update As Of Date icon to updatethe as-of date globally for requests that use the as-of date option.

To update the as-of date for one of the ledgers listed, enter the date inthe As of Date field in the Process Request Parameters row.

Retention Days Enter the number of retention days for the journal data. The system uses thissetting with the request date option to determine the archive date.

See Also

Chapter 20, “Archiving Ledgers and Journals,” Retention Days and Archive Date, page 440

Restoring Archived JournalsAccess the Journal Archive Request page.

Specify the business unit, the ledger group, and the restore as-of date (the date that thejournals were archived). When you restore archived journals, the system restores all thejournal data that was archived from the archive request.

Archive Option SelectRestoreto restore archived data. Enter a date in the Restore As of field.

Restore As-of Select a date from the archive log to restore

Viewing the Archive Journals LogAccess the Review Archived Journal Log page.



Review Archived Journal Log page

Unit Select the business unit whose archived journals you want to review.

Ledger Group Select a ledger group to view journals for a specific ledger group. To view allarchived journals for the business unit, leave the field blank.

As of Date Enter a date to view journals that have been archived as of a certain date.

Search Click to view selected archive log entries and statistics.

Archive Log Entries and Statistics Grid

Ledger Group Displays the ledger group whose journals were archived.

Status Displays the status. Values areArchiveandRestore.

Archive Date Displays the date that the journals were archived.

The archive process creates a log entry for each unique unit, ledgergroup, status, and archive date combination.

Last Update Date/Time Displays the date and time of the last update.

For example, if you have archived journals for a ledger group, restoredthem, and then archived them again using the same archive date, therewould be two listings for the ledger group—one with the statusArchiveand one with the statusRestore.TheArchivestatus line would havea later update date and time. Consequently, thecurrentstatus of thejournals in the ledger group would be archive.

The statistics for archived journals appear as entries.

Total Journals Displays the number of archived journals in the ledger group.

Total Lines Displays the number of journal lines.

Total Debits Displays the total debit amount for the archived journals.

Total Credits Displays the total credit amount for the archived journals.




CHAPTER 21

Using Commitment Control in PeopleSoftGeneral Ledger

This chapter provides an overview of the relationship between Commitment Controland General Ledger and how to:

• Enter and process commitment control journal entries in General Ledger.

• Enter and process commitment control journal entries with entry events in General Ledger.

• Review and correct journal entries with budget checking errors.

Understanding Commitment Control and GeneralLedger Journals

Budgetary control ensures that commitments and expenditures do not exceed total budgets. You set up yourcommitment control budgets and budget ledgers and link them to the actuals ledgers, which enables youto create journal entries in PeopleSoft General Ledger. This section provides an overview of:

• Commitment Control Journal Entries

• Commitment Control Journal Entries with Entry Events

• Journal Entries with Budget Checking Errors

PrerequisitesBefore you use Commitment Control with General Ledger:

• Read thePeopleSoft Setting Up and Using Commitment Control PeopleBook:“Understanding Commitment Control”chapter.

• Set up your system for commitment control accounting.

• Enable Commitment Control for PeopleSoft General Ledger on the Installation Options − Products Page.

• Set up ledger groups specifically for control budgets and link the budget ledgers to the ledgersrecording actual transactions (actuals ledgers) using the Ledger for a Unit page.

• Review the commitment control source transaction definition, GL_JOURNAL, created byPeopleSoft for general ledger. Do not change this definition.


Using Commitment Control in PeopleSoft General Ledger Chapter 21

See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “GettingStarted With Commitment Control”



Commitment Control Journal EntriesThe commitment control journal entry that you enter depends on the Commitment ControlAmount Type you select. When you select:

• Actuals and Recognized.

The journal transaction is recorded in the actuals ledger and the revenue or expenditurecommitment control ledger is updated.

• Pre-Encumbrance.

The pre-encumbrance amount is adjusted, the commitment control budget detail ledgeris updated, and the actuals ledger is not updated.

• Encumbrance.

The encumbrance amount is adjusted, the commitment control budget detail ledger isupdated, and the actuals ledger is not updated.

• Collected Revenue.

The collected revenue amount is adjusted, the commitment control collected revenue ledgeris updated, and the actuals ledger is not updated.

• Actuals, Recognize, Collected Revenue

A recognized or collected amount is updated in the actuals revenue ledger, and the appropriatecommitment control revenue estimate budget ledgers is updated.

Commitment control journal entries may be for interunit journals, reversals, allocations, revaluation, andtranslation journals that are set up for or linked to a commitment control ledger group. You process the journalonline or through batch processing. Once the journal entries are edited, Commitment Control Budget Processor(FSPKBDP3) checks the general ledger journals against control budgets to ensure that they comply with therules established for budgets. Budget processor may fail a transaction if it does not comply with the budget rules.Rules control whether or not spending may exceed a budget. It also verifies that you have valid ChartFieldsbased on the budget ledger(s) and updates these budget ledgers with the journal amounts. An error is generatedfor the transaction if there is problem, which you can correct before you continue with your processing. Ifeverything is correct, budget processor updates the budget amounts in the commitment control budget ledgers.

If you selected an actuals commitment control type prior to creating the journal entry, the detailaccounting transactions are posted to the actuals ledger, while the budget amounts are updatedin the commitment control budget ledgers by the budget processor.


Chapter 21 Using Commitment Control in PeopleSoft General Ledger

If you selected pre-encumbrance, encumbrance, or collected revenue, budget processor only updatesthe budget amounts in the corresponding commitment control ledger, and the actuals ledger is notupdated. If you want to adjust the specific budget amount as well as to create the appropriate budgetaryaccounting entry, you need to use entry event on the budget adjustment journal entry.

Note. If the Journal Edit process (GL_JEDIT) initiates the budget processor, it calls the FSPKBDP2 process.If you run the budget processor from the Budget Check Journals page, the FSPKBDP3 process runs.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “SettingUp Basic Commitment Control Options”.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “UnderstandingPeopleSoft Commitment Control”.

Commitment Control Journal Entries with Entry Events

Use entry events with commitment control journal entries, which use the GLJE entry event process, andcommitment control budget adjustment journal entries, which use the GLJEADJ entry event process.

See Chapter 23, “Using Entry Events in PeopleSoft General Ledger,” Understanding EntryEvents in PeopleSoft General Ledger, page 477.

Journal Entries with Budget Checking Errors

Correct errors by drilling down as far as the journal line details. Once you correct the budgetchecking errors, you must rerun budget processor.

See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “ProcessingSource Transactions Against Control Budgets”

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Managing Budget Exceptions”

Entering and Processing Commitment Control JournalEntries in General Ledger


• Enter header information for Commitment Control journal entries.

• Use Commitment Control amount types.

• Enter and process Commitment Control journal lines.



Pages Used to Enter and Process Commitment ControlJournal Entries in General Ledger


Create Journal Entries -Header

JOURNAL_ENTRY1 General Ledger, Journals,Journal Entry, Create JournalEntries

Select the appropriate ledgerand ledger group to apply tothis journal entry.

Commitment Control -Commitment ControlAmount Types

JOURNAL_ENTRY_KK Click the CommitmentControl link on the CreateJournal Entries - Headerpage.

Select a commitment controlamount type to determine thetype of processing requiredfor the journal entry lines.


JOURNAL_ENTRY2_IE General Ledger, Journals,Journal Entry, Create JournalEntries, Lines

Enter journal lines andChartField information tocreate a journal. You can runthe edit and budget checkprocess on-line.

Budget Check Journals JOURNAL_BGTCHK_REQ General Ledger, Journals,Process Journals, BudgetCheck Journals.

Runs the CommitmentControl Budget Processor tobudget check all edit-validcommitment controljournals.

Entry Event Journals PST_EE_RUN_REQUEST General Ledger, Journals,Process Journals, EntryEvent Journals

Run the Entry EventProcessor (FS_EVENTGENapplication engine) toprocess and generate entryevent accounting data forjournals with entry eventscodes that have not beenprocessed, such as budgetadjustment journals.

Generate Journals JRNL_GEN_REQUEST General Ledger, Journals,Subsystem Journals,Generate Journals.

Enter data to run JournalGenerator process(FS_JGEN applicationengine) to generate journalsfrom subsystems, accountingentries generated by EntryEvent Processor andimported data to post inGeneral Ledger.

Generate Journals RequestJRNL_GEN_REQUEST General Ledger, Journals,Subsystem Journals,Generate Journals

Runs the Journal Generatorprocess (FS_JGEN) to createjournals from subsystemaccounting lines.



Page Name Object Name Navigation UsagePost Journals JOURNAL_POST_REQ General Ledger, Journals,

Process Journals, PostJournals

Enter the information for thejournals you intend to post.Runs the PS/GL Journal Post(GLPPPOST) process tobatch post the journals totheir appropriate ledgers.When use entry event on thebudget adjustment journalentry, you have to post thecorresponding budgetaryaccounting entry created byJournal Generator.

Entering Header Information for Commitment ControlJournal EntriesAccess the Create Journal Entries − Header page. .

Journal Entry − Header page

Note. Actualsledger or ledgers refers to a part of PeopleSoft’sRecordingLedger Group shownin the sample data and is used to distinguish the actual transactions ledgers from the commitmentcontrol budget ledgers.Detailledgers refers to ledgers that record actuals, pre-emcumbrances,encumbrances, revenue and collected revenue amounts.

Ledger Group You can enter and post a journal directly against a commitment control ledgerby selecting a commitment control expenditure or revenue Ledger Group.

Ledger Select a detail Ledger within the group. If you select a Commitment ControlLedger group, you can create and post journals for the pre-encumbrance,encumbrance, recognize revenue, or collected revenue amounts against only



the commitment control ledgers. However, these amounts are not posted to theactuals ledger. To post any of these amounts in the actuals ledger, you mustmanually create the journal entries that post to your actuals ledger.

If you select a specific commitment control ledger group and detail ledger,then the selected detail ledger is the only ledger updated. If you selectan actuals ledger and then select the option to do a commitment controladjustment, all commitment control ledgers associated with this actuals ledgerin Ledgers For A Unit are updated if the adjustment applies.

Note. If you are only adjusting one specific commitment control ledger, select the commitment controlledger group and its detail ledger. This enables you to access the selected commitment control ledgersdirectly to create your adjustments. You do not have to select the Commitment Control link because thenature of the ledger group and detail ledger you selected automatically identifies the type of adjustment.However, if you select commitment control ledger group, you cannot specify entry event on the journalline. That means you have to manually create the corresponding budgetary accounting entry.

Using Commitment Control Amount TypesAccess the Commitment Control page.

Budget Processor (FSPKBDPx) determines how to update the control budget based on thecommitment control amount type that you select.

• You can update the commitment control budget ledgers and also post the journal to actuals ledger whenyou select the amount typeActuals and Recognizedor Actuals, Recognize and Collect

• You must select the commitment control amount typeEncumbrance, Pre-encumbrance,or Collected Revenueto make commitment control budget adjustments to these ledgerswithoutupdating the actuals ledger. Youmay use entry events to generate the corresponding budgetary accounting entry and post to the actuals ledger.

• You can also bypass commitment control budget checking or override commitment control budgetexceptions by selecting the Commitment Control link and enabling the appropriate check box.



Commitment Control link

Actuals and Recognized When you select this option, the journal records the transaction in the actualsledger and also in the appropriate Commitment Control ledger (expenditureor revenue) based on the ChartFields used in the journal line. Selectingthis type enables you to select the entry event codes on the journal linethat use the GLJE Entry Event Process. Select the commitment controlamount type that represents this journal. Budget Processor (FSPKBDPx)determines which commitment control budget ledger to update.

Encumbrance An encumbrance is an amount that you are legally obligated to pay basedon a contract or a purchase order. You select this option when you want toadjust the Commitment Control encumbrance ledger that affects your budgetamounts. After selecting this option, you return to the journal line, selectthe BUDJEADJ entry event code, which enables you to select the entryevent codes on the journal line that use the GLJEADJ entry event process,which include GL_JENC, GL_JPRNC and GL_JCREV Entry Event sourcetransactions. Enter the adjustments that you want to make to the CommitmentControl budget journal. When you edit and budget check this transaction,the encumbrance amounts is updated in the associated Commitment Controlbudget journal ledgers. You run the Entry Event Processor for this journalentry in batch mode to generate the accounting lines that you want updateand post in the actuals ledger. Then you run Journal Generator to createthe journals and post the journals to the actuals ledger.

See Chapter 23, “Using Entry Events in PeopleSoft General Ledger,”GLJEADJ Entry Event Process, page 480.



Note. If you specified a Commitment Control ledger group along with aCommitment Control ledger on the Journal Header page, the CommitmentControl amount type is already determined, and the CommitmentControl Amount Type page is not enabled.

Pre-Encumbrance A pre-encumbrance is the amount that you intend to spend when you create arequisition. You select this option when you want to adjust the CommitmentControl pre-encumbrance ledger that affects your budget amounts. Afterselecting this option, you return to the journal line, select the BUDJEADJentry event code, which enables you to select the entry event codes on thejournal line that use the GLJEADJ entry event process, which includeGL_JENC, GL_JPRNC and GL_JCREV Entry Event source transactions.Enter the adjustments that you want to make to the Commitment Controlbudget journal. When you edit and budget check this transaction, thepre-encumbrance amount is updated in the associated Commitment Controlbudget journal ledgers. You run the Entry Event Processor for this journalentry in batch mode to generate the accounting lines that you want updateand post in the actuals ledger. Then you run Journal Generator to createthe journals and post the journals to the actuals ledger.

Selecting this type enables you to select the entry event codes on the journalline that use the GLJEADJ entry event process, which includes GL_JENC,GL_JPRNC and GL_JCREV Entry Event source Transactions.

Note. If you specified a Commitment Control ledger group along with aCommitment Control ledger, the Commitment Control amount type is alreadydetermined, and the Commitment Control Amount Type page is not enabled.

Collected Revenue When you select this option, this journal records the amount of revenuecollected based on a previously entered revenue transaction. This updates theCollected Revenue ledger of a Commitment Control Revenue Budget.

Selecting this type enables you to select the entry event codes on the journalline that use the GLJEADJ entry event process, which includes GL_JENC,GL_JPRNC and GL_JCREV Entry Event source Transactions.

Actuals, Recognize andCollect

When you select this option, this journal records both the amount ofrevenue booked and the amount of revenue collected, and updates theRevenue Estimate Commitment Control Budget.

Selecting this type enables you to select the entry event codes on thejournal line that use the GLJE Entry Event Process.

Note. You can select entry event codes for Planned CommitmentControl amount type; however the Entry Event Processor will notprocess this Commitment Control amount type.

Planned Select this type to enable you to select the entry event codes on the journalline that use the GLJEADJ entry event process. However, the entry eventprocessor does not run for the codes you select on the journal line. Instead, the



journal amount that you plan to spend is recorded. This amount is only anestimate and is not yet an actual transaction and is updated in the PlannedCommitment Control ledger in the Commitment Control ledger group.

ByPass Budget Checking Select this option to allow the journal to bypass budget checking.

Note. If you select ByPass Budget Checking, the Entry Event processordoes not create accounting lines for the journal.

Override Select this option to allow the transaction to pass budget checking if thereare any overrideable exceptions exist for this journal, like the amountof the transaction exceeds the budget amount.

Override User ID If you selected the Override option and you override the budget for atransaction, the system updates this field with your User ID.

Override Date If you override a budget transaction, the system updates thisfield with the transaction date.

If the journal contains a journal line that has an account value that does not belong in the ledgerrepresented by the selected Commitment Control Amount Type, the budget processor will notprocess the line nor update the commitment control ledger data table. For example, if one journalline contains a revenue transaction, and you selected pre-encumbrances as the Commitment ControlAccounting Type, then budget processor will not process this line.

Entering and Processing Commitment Control Journal LinesAccess the Create Journal Entries - Lines page.

1. Enter the appropriate accounts, debit and credit amounts, and ChartFields for a commitment control journal.

Note. Depending on how your data is set up, you may be required to enter entryevent codes on the journal line.

See Chapter 23, “Using Entry Events in PeopleSoft General Ledger,” page 477.

2. Save the journal lines.

3. Select Process:Edit.

This process executes both the Edit and the Budget Check processes.

Note. If you are creating a budget adjustment journal, you are required to select an entryevent code that is associated with the GLJEADJ entry event process. The processing of thistype is different from the processing of GLJE entry event process.


4. Select Process:Budget Checkif you only need to execute the Budget Check process.



Note. When you increase the budget or change other budget options so that the journals thatfailed the budget check now pass, rerun the budget check processing again without changingthe journals, or rerun the Journal Edit process . If you change a journal after you run theJournal Edit and Budget Checking processes, you must rerun the Journal Edit and Budget Checkprocesses again to reflect the correct information on the budget.

5. If you delete a journal after you run the budget processor, the system calls the budget processorand reverses the entry to the control budget during the Delete process.

6. Once budget checking is successful, continue the posting process either on-line or in batch.

See Also




Enter and Process Commitment Control Journal Entrieswith Entry Events in General Ledger

To understand how to use entry events with commitment control journal entries:


Reviewing and Correcting Journal Entries withBudget Checking Errors


• Review and interpret commitment control journal status codes.

• Override journal entry budget checking errors.

• View journal header budget exceptions.

• View journal line budget exceptions.



Pages Used to Review and Correct CommitmentControl Journal Errors


Create Journal Entries− Lines


View the Budget Statuscode field for a specificcommitment control journalat the bottom of this page.This field is availableonly when the businessunit enabled commitmentcontrol.

Create Journal Entries -Errors

JOURNAL_ENTRY_E_IC General Ledger, Journals,Journal Entry, Create JournalEntries, Errors tab, or clickthe Errors tab on JournalEntry - Lines page, or clickthe Journal Status E (Errors)code link below the JournalStatus in the Totals groupbox on the Lines age.

View errors that occur inHeader and Lines page.

Journal Status - JournalLines

JOURNAL_LINE_FS General Ledger, Journals,Process Journals, ReviewJournal Status, Journal Lines.

View the budget status codefor commitment controljournals.

GL Journal Exceptions KK_XCP_HDR_GL1 Click the Budget Status Code(E) on the journal lines pageto access the GL JournalException page, or go toCommitment Control,Review Budget CheckException, General Ledger,Journal.

View budget check errorsor warning messages forgeneral ledger journals.Override the budgetexceptions if grantedauthority.

Exception Details KK_XCP_TRAN_SEC2 Click the View ExceptionDetailsbutton.

View the budget exceptiondetails for specifictransaction lines on thispage.

General Ledger Journal LineDrill Down

KK_DRL_GL1_SEC Click the Drill Down toTransaction Line button onthe Exception Details pagefor a specific journal line.

View the General LedgerJournal transaction lineentry.

Line Exceptions KK_XCP_LN_GL1 Commitment Control,Review Budget CheckException, General Ledger,Journal and click the LineExceptions tab to access theLine Exceptions page.

Use the GL JournalExceptions - LineExceptions page to viewindividual journal lines in ajournal with budget checkingerrors or warning messages.



Reviewing and Interpreting Commitment ControlJournal Status CodesYou can view the status for a specific journal on the Journal Entry − Lines page or the Journal Status −Journal Lines page. The status of the journal entry can be one of the following:

• E (error) The journal entry failed to pass budget checking. You must correct theerror before you can continue processing.

• N (not checked)Budget Processor (FSPKBDP3) has not processed the journal entry.

• V (valid) The entry passed budget checking and the process updated the control budget ledger.

Note. If you receive aW (warning) error, the budget header status is still valid.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Managing Budget Exceptions”.

Overriding Journal Entry Budget Checking ErrorsYou can override commitment control budget journal errors in two locations:

• Journal Entry −Header page.

• GL Journal Budget Exceptions pages.

Overriding Commitment Control Budget Journal Errors from theGL Journal Budget Exceptions Page

To override budget journal errors:

1. Access the Journal Entry − Lines page.

2. Click Budget Status to open the GL Journal Budget Exceptions page to override the budgettransaction in error and view details about the source transaction.

Note. You must have authority to override budget checking.

SeePeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “ManagingBudget Exceptions,” Handling Budgets with Exceptions.

See Also


PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Setting Up BasicCommitment Control Options,” Setting Up Control Budget Definitions

Viewing Journal Header with Budget ExceptionsAccess the GL Journal Exceptions page.

To define the GL Journal Exceptions Header information:



1. If you have super user security access (if security is not activated, anyone can select this check box),select the Override Transaction check box before or after running a budget check to update thecontrol budget for an entire transaction, even if exception errors exist. This option is not availableif the transaction passed budget checking with only warning exceptions.

2. Click the Advanced Budget Criteria link to open the Refine Inquiry Criteria page where you can restrictrows to specific business unit, ledger group, and account. Leaving these fields blank returns all values.

3. When you click Search to refresh the scroll area and select More Budgets Exist , the journal has moreexceptions than the number you entered in the Maximum Rows field. To display these additional budgets,modify either the Maximum Rows field to increase the number of budgets withErrors or Warnings.


Using the Budget Override Tab

To use the Budget Override tab:

1. Select Override Budget to update the control budget even though the transaction amount is exceedsthe budget amount. This field is available only if the budget transaction failed budget checkingand you have authority to override a budget entry. It is not available if the source transaction typedoes not allow overrides and the Budget Header Status isN(Not Checked). When you override thebudget exception, the system populates the Override User ID field with the user ID of the personwho overrode budget checking and the Override Date field with the date and time of the budgetexception override. The journal passes budget checking when you override all the budgets withexceptions, change the budget available amount, or change the journal amount.

2. Click View Related Links to access the Go to Budget Exception link and the Go to Budget Inquiry link.

3. Click the Go to Budget Exception link display the Budget Exception page. You can viewand override additional transactions that have exceptions for the budget. You must beauthorized to inquire on the budget and open this page.

4. If you click Go to Budget Inquiry, the Budget Details page opens. You can view thebudget’s details, such as the available amount remaining, the attributes, and the amountsused by each ledger (encumbrance, pre-encumbrance, and others) in the budget. You mustbe authorized to inquire on the budget to open this page.

5. Return to the Budget Override tab and click View Exception Details to drill down to theGeneral Ledger Journal Line for this budget exception.


Reviewing the Budget ChartFields Tab Information

To review the Budget ChartFields:

1. Click the Budget ChartFields tab on the GL Journal Exception page.

2. Review the ChartFields defined for the budget containing the exception. BudgetChartFields vary for different budgets.

3. Click View Exception Details to drill down to the General Ledger journal linedetails for this budget exception.




Drilling Down to the Budget Exception’s General Ledger Journal Line Details

To drill down to the General Ledger journal line:

1. On the GL Journal Exceptions page − Budget Override tab or the Budget ChartFields tab, clickView Exception Details to open the Exception Details page, which contains the Transaction Header,and the Budget Exception Details and the Transaction Line information.

2. On the Budget Exception line, click the Drill Down to Transaction Line to review theGeneral Ledger Journal Line Drill Down page.

3. Review the Transaction Line Identifiers group box information, which describes the source transaction datasuch as the business unit, ledger group, GL journal ID, journal date, and the journal line number.

4. Review the Transaction Line Details group box information, which describes the detail information forthe budget that appear in the journal line such as ChartField name, value, and description.


See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Setting UpCommitment Control Source Transaction Types”

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Setting Up BasicCommitment Control Options,” Setting Up Control Budget Definitions

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Setting Up Basic CommitmentControl Options,” Understanding Basic Commitment Control Setup

Viewing Journal Lines with Budget ExceptionsAccess the Line Exceptions page.

Limiting the Number of Budget Line Exceptions

To limit the number of budget line exceptions:

1. Use the Line Status field to limit the rows of budget line exceptions to eitherError or Warningexceptions.

2. To view a range of lines, enter the source transaction line numbers in the Line From and LineThru fields. The prompt list only displays journal lines with exceptions.

3. When you click Fetch Selection to refresh the scroll area, and the More Lines Exist check boxis selected, this means the source transaction has more exceptions than the number you enteredin the Maximum Rows field. Modify either the Maximum Rows field or the Line From andLine Thru criteria to increase the number of journal lines with error or warning exceptions todisplay in the Transaction Lines with Budget Exceptions scroll area.

4. In the Transaction Lines with Budget Exception group box, click the Line Values tab to list and inquireabout the journal lines that have budget exceptions for a specific business unit, budget date, and ledger.



5. Click the Line ChartFields tab to list and inquire about journal line ChartField values that have budgetexceptions. The number of ChartFields on a line varies based on the original budget setup.

6. Click the Line Amount tab to list and inquire about the journal line amounts that have budgetexceptions. The Foreign Amount is the amount entered on the journal line in its enteredcurrency. The Monetary Amount is the amount in the base currency of the ledger. The Quantityis the statistical amount, which may appear, if applicable.

7. Click View Exception Details on each of the tabs to open the Exception Details page. Thispage contains the Transaction GL Journal Line Number and Ledger , the Budget ExceptionDetails and the Budget Items information for this journal line. Click the Budget ChartFields tabto view the ChartFields associated with the journal line’s budget. Click the Budget Overridetab to override the budget associated with this journal line.





CHAPTER 22

Approving Journal Entry

This chapter provides an overview of the journal entry approval process and discusses howto set up journal entry approval in PeopleSoft Workflow.

Understanding the Journal Entry Approval ProcessIn PeopleSoft General Ledger, anapprovedjournal is one that is marked to post. You can allowspecific users to mark a journal to post by granting them access to certain pages in Operator Securityor by approving journals through PeopleSoft Workflow using the Virtual Approver. Businessprocess maps are useful tools to use to define your workflow process.


• Business process maps and PeopleSoft Workflow.

• Journal entry approvals using PeopleSoft Workflow.

• Journal entry approvals using PeopleSoft system user security.

Business Process Maps and PeopleSoft WorkflowThe PeopleSoft system enables you to define graphical, process-based maps to illustrate how a particulartask fits into the business process and to quickly navigate to the pages that you need. You can create mapswhile building workflow into business processes. You can also build business processes toimplementworkflow even if you do not intend to use the business processes to navigate the system.

See Also

PeopleTools PeopleBook: PeopleSoft Workflow Technology, "Designing PeopleSoft Navigator Maps"

Journal Entry Approvals Using PeopleSoft WorkflowFollow these steps to organize and set up data to approve journal entries using workflow:

1. Define the roles and user profiles.

Specify who performs each activity. Define the roles that people perform in the workflow,as well as information about the people who fill the roles. This information enables thesystem to route work items to the appropriate users.

2. Define or modify the business process.

Define or modify the process name, description, activities, worklists, business events, and routings.


Approving Journal Entry Chapter 22

3. Define or modify the approval rule set.

Define who has authority to approve a journal and the approval limits.

4. Assign approval rules to business units, ledger groups, and journal sources.

You can have as many business processes and approval rules as you want. Assign them tothe appropriate business units, ledger groups, and journal sources. If you do not want to useworkflow approvals, use the default value, which isPre-Approved.

Note. When you define approval rules at the source level, they override any approval handlingthat you specified at the ledger group and business unit levels. Any rules specified at theledger level override those at the business unit level.

The PeopleSoft system comes with a sample approval rule called JOURNAL_ENTRY_APPROVAL for theJournal Entry Approval business process. You activate this sample rule in PeopleSoft Application Designer.

Journal Entry Approval Workflow Definition Setup

The business process delivered in the sample data contains the activity APPROVE_DENY_JOURNAL, which comprises four events:

Event Name Map Label Description

Journal Entry Approval Further Approval Required Generates a worklist entry for thenext user in the approval hierarchy.

Journal Entry Denial Journal Entry Denied Sends an email to the previous user.

Journal Entry Recycle Journal Entry Recycled Generates a worklist entry for theprevious user.

Marked to Post Journal Entry Approved Indicates that the journal is approvedand marked to post. (This event isnot tied to the sample approval rule.It exists merely for documentationpurposes.)

To approve journal entries through PeopleSoft Workflow, you must configure definitions andrules. For example, to generate an emailand a worklist entry for journal entry denials, modifythe activity definition in PeopleSoft Application Designer. To require that two supervisors anda manager approve journals, change the approval rule set in Application Designer. The samplebusiness process that comes with the system is JOURNAL_ENTRY_APPROVAL, and theapproval rule set definition is named JOURNAL_ENTRY_APPROVAL. You can modify thesedefinitions or use them as templates for your own definitions.


Chapter 22 Approving Journal Entry

Warning! To approve journal entries using PeopleSoft Workflow, you must clear the Mark Journal(s)to Post check box on the User Preferences - General Ledger page. You must also hide the MarkJournal(s) to Post option on the Edit Journal Request page by replacing the entire content ofJRNL_EDIT_REQ.MARK_POST_OPTN RowInit PeopleCode with the following code:

JRNL_POST_OPTN = "N";

Hide (JRNL_POST_OPTN);

MARK_POST_OPTN = "N";

Hide (MARK_POST_OPTN);

Note. You cannot post an online journal that needs approval.

Virtual Approver

The Virtual Approver has three actions associated with journal approvals. When invoked, the VirtualApprover returns a status based on the action specified and the authority of the user. The status isstored in the Journal Process Request field on the Journal - Header page.

Approval Action Process Status

Approve Approved(marked to post) orPending Approval

Deny Denied

Recycle Pending Approval

Journal Edit processes all journals—even those markedDeniedor Pending Approval.JournalPost posts only those journals that are marked to post (Approved) and marked valid by JournalEdit. Online edits prevent an unedited journal from being approved.

The sample Journal Entry Approval rule uses a two-step approval process. Members of two roles—supervisorsand managers—can approve journals. Supervisors can approve amounts from –1,000.00 up to 1,000.00.Managers can approve from –100,000.00 up to 100,000.00. Both supervisors and managers must haveauthority for the journal header business unit and the administrative area defined for the business process.

When you select the Submit Journal option in the process list on the Journal Entry - Lines page, theVirtual Approver determines whether you are authorized to approve the journal. If you do not selectit, the Virtual Approver prompts you to send the journal into PeopleSoft Workflow. Worklist entriesare created for supervisors belonging to the administrative area GL with access to the business uniton the journal header, and the journal status is set toPending Approval.

If you are a supervisor, the Virtual Approver determines whether you are authorized to approve theamount in the total fields and the business unit. If so, the Virtual Approver returns the statusApproved,and the journal is marked to post. If you do not have authority to approve the journal, the VirtualApprover returns the statusPending Approval,and a worklist entry is generated for managers meetingthe administrative area and business unit criteria specified in the approval rule set.



When managers or supervisors select a worklist entry for journal approval or journal recycling, theyneed to access the Journal Entry - Approval page. Typically, you grant security access to this pageonly to people who have authority to approve the journal. On this page, you can approve, deny,or recycle the journal. You can also add comments to denial emails.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining Financials and Supply ChainManagement Common Definitions,” Specifying Approval Options for the Journal Source

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,”Defining Journal Approval Options for a Ledger

Chapter 22, “Approving Journal Entry,” Setting Up Journal Entry Approval in PeopleSoft Workflow, page 468

PeopleTools PeopleBook: PeopleSoft Workflow Technology , "Defining Approval Processes"

Journal Entry Approvals Using PeopleSoft System SecurityYou can also authorize approvals using the PeopleSoft system security for users that PeopleToolsprovides. Using this method, you grant access to key pages and processes to specific users. Forexample, the key pages for marking a journal to post and posting are the Mark Journals for Postingpage, the Edit Journal Request page, and the Post Journals page.

To prevent specific users from marking a journal to post, you do not assign them to a role that has access tothese pages. If the user is not permitted to use the Journal Edit Application Engine process (GL_JEDIT) orthe Journal Post COBOL process (GLPPPOST), a message displays informing them that they have notbeen authorized edit or post a journal using the options on the Journal Entry - Lines pages.

If you employ the user security approach for journal approvals rather than PeopleSoft Workflow,ensure that the Approval Active option in the properties is not selected for the approval rule setJOURNAL_ENTRY_APPROVAL in PeopleSoft Application Designer. You can remove the ApprovalWork page (APPR_WRK_01) and Workflow Functions page (WF_FUNCTIONS_01) from theJournal Entry component (JOURNAL_ENTRY_IE) in Application Designer, because removingthese pages decreases the number of cache files that are built when you access the componentfor the first time. Removal of these pages, however, is not required.

Note. By default, the Approval Check Active check box is cleared when you receivethe approval rule in the sample data.

See Also

PeopleTools PeopleBook: PeopleSoft Security, "Understanding PeopleSoft Security"

Setting Up Journal Entry Approval in PeopleSoft WorkflowThis section discusses how to:



• Review the current workflow approval setup.

• Modify the workflow approval rule properties.

• Modifying the rule set definition properties for a workflow item.

• Defining the rules for a journal entry approval workflow item.

• Setting up the events for a journal entry approval workflow item.

See Also

PeopleTools PeopleBook: PeopleSoft Workflow Technology, "Defining Approval Processes"



Pages Used to Set Up Journal Entry Approvalin PeopleSoft Workflow


Open Definition Not applicable (NA) Access PeopleSoftApplication Designer andclick File, Open.

Select Approval Rule Setin the Definition field todisplay a list of ApprovalRule set definitions.

JOURNAL ENTRYAPPROVAL

NA Enter JOURNAL ENTRYAPPROVAL in the Namefield or click this name in thelist of Definitions matchingthe selection criteria box onthe Open Definition page,and click the Open button.

The JOURNAL ENTRYAPPROVAL (Approval RuleSet) page displays.

Approval Rule N/A Right-click in the JOURNALENTRY APPROVALpage and select DefinitionProperties to display theApproval Rule Propertiespage.

Select the Approval Activecheck box on the GeneralTab page to activate theVirtual Approver.

Approval Rule SetDefinition

NA Click one of the icons(Supervisor Approval,Manager Approval) inthe JOURNAL ENTRYAPPROVAL page, and selectItem Properties.

Accesses the Approval RuleSet Definition.

Approval Rule SetDefinition - Definition

NA Access the rule stepDefinition by clicking one ofthe icons in the approvalrule set and selecting ItemProperties.

Set up or modify theapprover roles that applyto journal entry approvalworkflow process as well asthe workflow process steps.

Approval Rule Set - Rules NA Click the Rules tab onthe Approval Rule SetDefinition page.

Sets up the minimum andmaximum amounts that youcan use in selected journalrecords and fields, as well asthe minimum and maximumquantities. Also identifieswhether the row-level rulesare determined by routecontrol or SQL object.

Approval Rule Set - Events NA Click the Events tab onthe Approval Rule SetDefinition page.

Use to associate journalapproval activities withworkflow events.

Reviewing the Current Workflow Approval SetupIn PeopleSoft Application Designer, access the JOURNAL_ENTRY_APPROVAL.1900–01–01 approval ruleset by selecting File, Open and then clicking the approval rule set name in Open Definition dialog box.



JOURNAL_ENTRY_APPROVAL.1900–01–01 approval rule set

Supervisor Approval andManager Approval

These icons represent the workflow for approving a journal entry thatis delivered with the sample data. You can click on the items andmodify the workflow journal entry approval rule properties or theselected icon’s workflow rule set definitions.

Modifying the Workflow Approval Rule PropertiesAccess the properties for the approval rule by right-clicking in the approval rule setwindow and selecting Definition Properties.



Approval Rule Properties page

Approval Active Select this check box to activate the journal entry approvalprocess using workflow.

Modifying the Rule Set Definition Properties for a Workflow ItemAccess the rule step definition by clicking one of the icons in the approval rule set and selecting Item Properties.



Rule Step Definition page

Icon Descr(icon description) Modify the workflow icon description.

Route to Role Select a different role to apply to the icon.

Equally Authorize Roles Modify the current role and click Add to add more than one approver for therole, or click Remove to remove an approver role. For example, you mighthave two managers approve a journal entry before the supervisor approves it.

SeePeopleTools PeopleBook: PeopleSoft Workflow Technology

Defining the Rules for a Journal Entry Approval Workflow ItemSelect the Rules tab in the Rule Step Definition window.



Rule Step Definition - Rules tab

Amount Rule Enter the minimum and maximum amounts for a specific record and field.

Quantity Rule Enter the minimum and maximum quantity (for statistical journalentries) for a specific record and field.

Row-level Rule Select the appropriate radio button if the row-level activity is basedon route control or a SQL object.

If you select Route Control, enter the route control name and itsrelated record and field values.

If you select SQL Object, enter the SQL object name and therelated record and field values.

Setting Up the Events for a Journal Entry Approval Workflow ItemSelect the Events tab in the Rule Step Definition window.



Rule Step Definition - Events tab

On Pre-Approved Select the activity and event that you want to occur when ajournal entry is preapproved.

On Deny Select the activity and event that you want to occur when ajournal entry is denied approval.

On Recycle Select the activity and event that you want to occur when a journalentry is recycled for approval.




CHAPTER 23

Using Entry Events in PeopleSoft General Ledger

This chapter provides an overview of entry events in PeopleSoft General Ledger and discusses how to:

• Use the GLJE Entry Event process.

• Use the GLJEADJ Entry Event process.

• Correct entry event journal errors.

Understanding Entry Events in PeopleSoft General LedgerUse entry events in PeopleSoft General Ledger to post additional debit and credit accounting entries. Inaddition, federal agencies can update budgetary as well as proprietary accounts in a single transactionor update the budgetary ledgers without posting to the actuals ledger.


• PeopleSoft General Ledger entry event transactions.

• Entry event source definitions, processes, steps and codes.

• GLJE Entry Event process.

• GLJEADJ Entry Event process.

• Multibook ledgers using entry events.

• Intra/Interunit journal entries using entry events.

• Allocations using entry events.

• Standard journal entries using entry events.

• Separate debit and credit journal entries using entry events.

• Flat file journal imports using entry events.

• Spreadsheet journal imports using entry events.

• Copy entry event journals.

• Entry event journal errors.

PrerequisitesBefore using entry events in PeopleSoft General Ledger, you must:

1. Perform the normal setup activities for PeopleSoft General Ledger and the Commitment Control feature.


Using Entry Events in PeopleSoft General Ledger Chapter 23

2. For PeopleSoft General Ledger, in the Entry Event field on the Installation Options -Entry Event page, select eitherOptional or Required.

3. Only for GLJEADJ — Commitment Control Adjustment Journals do you need to Enable theCommitment Control feature for PeopleSoft General Ledger in the Enable Commitment Controlgroup box on the Installation Options - Installed Products page.

4. Select Allow GL Entry Event Bypass for selected users on the User Preferences- General Ledger page, if desired.

This option enables specific users to bypass selecting entry event codes that are identified asrequired for General Ledger on the Installation Options - Entry Event page.

5. Select Skip Entry Event Processing in the Budget Post Options group box for selected userson the User Preferences - General Ledger page, if desired.

This option enables specific users to post a budget without running the Entry EventProcessor Application Engine process (FS_EVENTGEN).

6. Verify that the ledger group for entering journal entries with entry events (normally theactuals ledger group, which is named the Recording ledger group in the predefined data)is associated with the standard ledger group type.

This is the only ledger group type that you can use to enter entry events forPeopleSoft General Ledger journal entries.

Note. If you plan to create multibook journals with entry events, make sure that all of themultibook ledgers are set up, that the ledger group type is set to standard, and that you select theKeep Ledgers in Sync check box on the Ledger Groups - Definition page.

7. Refer to the documentation regarding the setup of the entry event codes for an organization based on theentry event source transactions and processes that are predefined for PeopleSoft General Ledger.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Using Entry Events”.

Note. You can create your own entry event codes that use the predefined source transactionsand processes; however, do not modify the predefined data.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Using Entry Events,” Setting Up Entry Events

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Setting Installation Options for PeopleSoftApplications,” Enabling Entry Events at the Installation Level

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining User Preferences,” Defining Overall User Preferences

PeopleSoft General Ledger Entry Event TransactionsPeopleSoft General Ledger enables you to enter, process, copy, and correct entry event transactions using:


Chapter 23 Using Entry Events in PeopleSoft General Ledger

• Online journal entries.

• Batch journal entries.

• Commitment Control budget adjustment journal entries.

• Multibook journal entries.

• Allocations.

• Interunit and intraunit journal entries.

• Standard journal entries.

• Separate debit and credit journal entries.

• Imported flat file journals.

• Imported spreadsheet journals.

Note. Do not associate entry event codes with open item accounts for use in open item entries. Also, do notassociate entry event codes with value-added tax (VAT) or VAT-applicable accounts. The entry event codedefinition does not allow the selection of VAT-applicable accounts for entry event processing. If a journal comesfrom an external source (such as a flat file or spreadsheet), the appropriate account from the entry event codedefinition overwrites any accounts specified on the entry event lines that subject to GLJE Entry Event process.

Entry Event Source Definitions, Processes, Steps, and CodesPeopleSoft General Ledger provides the sample data with a set of predefined entry event codes. Youcan use these predefined codes as an example to define your own codes. The system has predefinedentry event source definitions and specific entry event processes that you must not change. The sourcedefinitions identify the source and target records that the system updates when the Entry Event Processorprocess runs. The predefined source definitions for General Ledger are:

• GL_JCREV - GL Adjustment Journal Collected Revenue.

• GL_JENC - GL Adjustment Journal Encumbrance.

• GL_JOURNAL - GL Journal.

• GL_JPRNC - GL Adjustment Journal Pre-encumbrance.

• GL_JRNLIU - GL Journal IU Transactions.

Entry event source definitions, processes, and steps determine the way in which the entry event codes areprocessed. The processing procedures for creating journal entries with entry events and creating budgetadjustment journal entries are unique due to the specific entry event source transactions and entry eventprocesses and steps that are linked to each entry event code. Multiple entry event source transactions, suchas GL_JOURNAL and GL_JRNLIU (for interunit transactions), can be associated with one entry eventprocess, such as the GLJE Entry Event process or the GLJEADJ Entry Event process. Subsequently, the EntryEvent Processor process can generate journal lines for a normal journal entry, an interunit journal entry, or astandard journal entry, depending on the source transaction associated with the entry event process.



GLJE Entry Event ProcessThe GLJE Entry Event process is used for most types of entry event journal entries. When an entryevent code is associated with the GLJE Entry Event process, you can generate additional debit and creditentries beyond the entries that user entered by Journal Edit process for accounting.

Note. In a journal that uses the GLJE Entry Event process, the account from the entry event codeappears by default in the first journal line unless the entry event code has been setup for IU processingas well. When you run the Journal Edit process (GL_JEDIT), the Entry Event Processor process runsautomatically during the edit process and generates the additional entry event lines.

• Run the Journal Edit process.

The Journal Edit process runs the Entry Event Processor process.

• Run the Budget Processor process if commitment control is enabled for the business unit and ledger group.

• Post to PeopleSoft General Ledger actuals ledger.

GLJEADJ Entry Event ProcessYou associate the GLJEADJ Entry Event process with an entry event code to make CommitmentControl budget adjustments for encumbrances, pre-encumbrances, and collected revenue budgets aswell as to generate and post the appropriate budgetary accounting entries to the actuals ledger. TheGLJE Entry Event process and the GLJEADJ Entry Event process function differently.

After you enter the debit and credit lines and select an entry event code for each line and finish Journal Edit:

• Run Budget Processor process to update the appropriate Commitment Control budget ledger table andadjust either the pre-encumbrance, encumbrance, or collect revenue amount of the budget.

• Run the Entry Event Processor process to generate the budgetary accounting entriesthat need be posted to the actuals ledger.

• Run the Journal Generator Application Engine process (FS_JGEN) to create the budgetaryaccounting journal from the budgetary accounting entries.

• Post the budgetary accounting journals to the appropriate actuals ledger.

When you enter the budget adjustment journal entries and select an entry event code that is set up withthe GLJEADJ Entry Event process, you must enter the debit and credit entries, because the JournalEdit process does not run the Entry Event Processor process to generate the remaining journal lines asit does for the GLJE Entry Event process. After journal edit processes, you run the Budget Processorprocess to update the appropriate Commitment Control budget ledger table and adjust the specificcontrol budget’s ledger amount. After the journal lines are successfully edited and budget-checked eitheronline or in batch, you must run the Entry Event Processor process (using the Process Journals menu)to generate the budgetary accounting entries, based on the accounts that you set up for the selectedentry event code. After processing the entry events, you run Journal Generator process to generate thebudgetary accounting journal and post this journal to the appropriate actuals ledger.

Note. In PeopleSoft General Ledger, the entry event source definitions, entry event processes andsteps, and entry event codes are predefined. Do not change them.



See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Entering andPosting Commitment Control Budget Journals”

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “Closing andWithdrawing Commitment Control Budgets”


Multibook Ledgers Using Entry EventsTo enter entry events for multibook journals:

1. Enter one side of the journal entry by selecting an entry event code for a ledger group that containsmultiple ledgers and for which the Keep Ledgers in Sync check box is selected.

2. Run the Journal Edit process.

When you enter the journal line, you typically enter only one side of the journal if you are using entryevents for the GLJE Entry Event process. The Journal Edit process generates the additional entryevent lines for the primary ledger. It also matches journal lines for all secondary ledgers within theledger group using the same entry event code. This is a multibook journal entry.

Note. If the journal is from an external source and does not already have secondaryledger lines, Journal Edit process will create the secondary ledger lines and call the EntryEvent Processor process to create the entry event lines.

3. Continue to process and post the multibook journal.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Setting Up and Using Multibook Ledgers

Chapter 15, “Processing Multiple Currencies in PeopleSoft General Ledger,” Using MultiCurrencyProcessing in a MultiBook Environment , page 301

Interunit Journal Entries Using Entry EventsWhen you run the Journal Edit process on an interunit or intraunit journal entry with entry events, it processesall of the journal header and journal lines associated with the interunit or intraunit journal lines first.



The Entry Event Processor process creates accounting entries from the interunit and intraunit entriescreated by the Journal Edit process. To enable this functionality, the entry event code must have theGLJE Entry Event process included in the setup, as well as the steps required by the transaction such asGLJEIUINP for interunit payables journal entries. It is possible to set up an entry event code to processregular journal entries and interunit and intraunit entries. If an entry event code has been set up with boththe regular process step and the intra/interunit process steps, the following logic is applied to the journal: Ifno interunit or intraunit lines are created in the journal, the entry event lines are created using the regularprocess step. If interunit or intraunit lines are created within the journal, the entry event lines are createdusing the intra/interunit process steps only. If the journal has both interunit and intraunit lines and noninterunit or intraunit lines, then intra/interunit process steps are used for entry events only.

The PeopleSoft system comes with a separate entry event source definition to enable you to useentry events with interunit and intraunit journal entry transactions:

Entry event source transaction:GL_JRNLIU.

Source record:EE_JRNL_LN_IUVW.

Target record:JRNL_LN.

Temporary record:EE_JRNL_TMP.

Four predefined process steps are used to process receivables and payables interunitand intraunit journal entry transactions:

• GLJEIUINP - Jrnl InterUnit Payable.

• GLJEIUINR - Jrnl InterUnit Receivable.

• GLJEIUIUP - Jrnl IntraUnit Payable.

• GLJEIUIUR - Jrnl IntraUnit Receivable.

Entry event processing for PeopleSoft General Ledger interunit and intraunit transactions is slightlydifferent from regular (predefined process step GLJE) journal processing for entry events. By design,interunit and intraunit lines are always balanced. Entry events in turn create balanced DR/CR pairsfrom the generated interunit and intraunit lines. If there is a need to create additional DR/CR pairsfrom interunit and intraunit transactions, you can establish only interunit payables, only interunitreceivables or both. The same is true for intraunit payables and intraunit receivables. One orboth transactions can be set up to generate balanced DR/CR pairs.

Note. If the inter/intraunit journal does not have an anchor business unit line, the system-generatedanchor business unit line will not have an entry event code, which means that the systemwill not generate extra debit/credit (DR/CR) lines.

See Also


PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Using Interunit and Intraunit Accountingand ChartField Inheritance,” Running the Centralized Interunit and Intraunit Processor



Allocations Using Entry EventsTo create allocation journals with entry events:

1. Specify the entry event field on the Define Allocation Step - Target page.

Note. Although you can also specifyEntry Eventas a field value on the Offset page, do not do so for regularjournal processing because you normally generate a one-sided journal entry from allocations when you useentry events in this situation. The Entry Event Processor process creates the other side of the journal entry.

2. Add a line to the Specify Field Values group box.

3. SelectEntry Eventas the field name,Valueas the source, and an entry event codeas a value to create output journals.

4. Save the allocation step.

5. Select Request Allocation to create the allocation output journals.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Processing Allocations”

Standard Journal Entries Using Entry EventsStandard journal entries are sometimes referred to astemplateor recurring journals. When you createstandard journals, the system copies the entry event source lines, as well as any non entry event lines,and the entry event status of the header and lines is set toN (not generated). This means that you mustrun the Journal Edit process for these journals to regenerate the entry event lines.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Creating SJEs, page 147

Separate Debit and Credit Journal Entries Using Entry EventsIf you select the Separate DR/CR Amount Fields check box on the Ledgers for a Unit - Definitionpage for a ledger, the Entry Event Processor process determines whether this is a normal journalentry or a journal entry reversal based on information on the journal line. For example, if you entera negative amount in the DR column, you indicate a reversal of a debit to the system. The EntryEvent Processor process generates the appropriate debit or credit journal lines.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Setting Up Ledgers,”Defining Default Journal Post Options for a Ledger



Flat File Journal Imports Using Entry EventsWhen you load journals containing entry events into PeopleSoft General Ledger by selecting ImportJournals, External Flat Files and running the Flat File Journal Import process, this process sets the entryevent status of header and any lines with an entry event code toN (not generated). If there is a mismatchbetween the entry event code and the account uploaded, the account is overwritten by the default accountwhen the Journal Edit process and the Entry Event Processor process are run.

See Also


Spreadsheet Journal Imports Using Entry EventsTo import and run spreadsheet journals containing entry events:

1. Select Import Journals, Spreadsheet Journals to load spreadsheet files that contain entry events.

2. Run the Spreadsheet Journal Import process.

This process sets the entry event status of header and each line with an entry event code toN(notgenerated). Consequently, you must run the Journal Edit process for these journals.

See Also


Copy Entry Event JournalsWhen you select Journal Entry, Copy Journals to copy journals using entry events, the Journal Copyprocess copies only the entry event source lines and the non entry event lines.

This process sets the new journal entry event status of header and each line with an entryevent code toN (not generated), which means that you must run the Journal Edit processthat automatically runs the Entry Event Processor process.

See Also

Chapter 8, “Making General Ledger Journal Entries,” Copying Journal Entries , page 154

Entry Event Journal ErrorsWhen you create journals with entry events and an error occurs during the processing, you candrill down to the transaction line to correct the entry event error and continue processing. Whenyou run the journal edit batch process which has errors, the process generates a report that containserrors that apply to both the journal entries and the entry events.

Creating and Processing Journal Entries with Entry EventsThis section discusses how to:



• Create and process entry event journals using the GLJE Entry Event process.

• Create and process entry event journals using the GLJEADJ Entry Event process.

The GLJE Entry Event process enables you to create journals that post to the actuals ledger.

• GL_JOURNAL - GL Journal.

• GL_JRNLIU - GL Journal Interunit Transactions.

You can modify the delivered entry event codes or set up your own.

Note. Do not modify entry event source definitions or processes and steps.

See Also


Pages Used to Create and Process Journal Entrieswith Entry Events


Create Journal Entries -Header

JOURNAL_ENTRY1 General Ledger, Journals,Journal Entry, Create JournalEntries, Header

Enter the journal headerinformation for entry eventjournal entries.

Commitment Control -Commitment ControlAmount Types

JOURNAL_ENTRY_KK Click the CommitmentControl link on the CreateJournal Entries - Headerpage.

For a Commitment Controlbudget adjustment journalentry, select the appropriateCommitment Controlamount type.



Select the Lines tab.

Enter the journal lineChartFields and select theappropriate entry eventcodes for processing.

Edit Journals Request JOURNAL_EDIT_REQ General Ledger, Journals,Process Journals, EditJournals, Edit JournalsRequest

Edit the regular journals andjournals using the GLJEand GLJEADJ Entry Eventprocesses.

Budget Check JournalsRequest

JOURNAL_BGTCHK_REQ General Ledger, Journals,Process Journals, BudgetCheck Journals, BudgetCheck Journals Request

Budget-check regularjournals and journals usingthe GLJE and GLJEADJEntry Event processes.

Entry Event Journals PST_EE_RUN_REQUEST General Ledger, Journals,Process Journals, EntryEvent Journals, Entry EventJournals

Run the Entry EventProcessor process forCommitment Control budgetadjustment journals usingthe GLJEADJ Entry Eventprocess.



Page Name Object Name Navigation UsageGenerate Journals RequestJRNL_GEN_REQUEST General Ledger, Journals,

Subsystem Journals,Generate Journals, GenerateJournals Request

Run the Journal Generatorprocess to generate journalsfor any journal entries notcreated online in PeopleSoftGeneral Ledger and forCommitment Controlbudget adjustment journalentries with entry eventsusing the GLJEADJ EntryEvent process.

Mark Journals for Posting JOURNAL_POST_MARK General Ledger, Journals,Process Journals, MarkJournals for Posting

Specify which journalsto post.

Post Journal Request JOURNAL_POST_REQ General Ledger, Journals,Process Journals, PostJournals, Post JournalRequest

Enter the information for thejournals that you intend topost. Run the PS/GL JournalPost process (GLPPPOST)to post the journals to theirappropriate ledgers.

Creating and Processing Entry Event Journals UsingGLJE Entry Event ProcessTo create and process an entry event journal:

Note. These steps use the JRNL1 entry event code.

1. Access the Create Journal Entries - Header page.

2. Select an actuals ledger group that may or may not linked to Commitment Control ledgers, andenter any other information relevant to the journal entry transactions.

The ledger group in the predefined data is Recording.

3. Click the Commitment Control link.

4. Select one of the following Commitment Control amount types, and then click OK:

• Actuals and Recognized.

• Actuals, Recognize and Collected.

See Chapter 21, “Using Commitment Control in PeopleSoft General Ledger,” page 449.

5. Access the Create Journal Entries - Lines page, and select the entry event code.

6. The account and alternate account values appear by default (after a server trip) in journal line 1from the values set up for the entry event code (for example,JRNL1) on the Entry Event CodeDefinition page if the entry event code contains regular process step GLJE.

Enter any other relevant data in the journal line.

Note. If you change either of these accounts, the system overwrites it with the default DR/CR account oralternate account when you edit the journal if the entry event code contains regular process step GLJE.



7. SelectEdit Journal to save and edit the journal entry as well as initiate the BudgetProcessor if commitment control is enabled.

Journal Edit process (GL_JEDIT) creates any missing lines before calling the Entry Event Processor process.

The Entry Event Processor process generates the additional journal lines based onthe set up for the selected entry event code.

The Budget Processor process runs to verify that a Commitment Control budget is associated withthe transaction and that the amounts are not greater than the budget amounts.

8. SelectPost Journalto post the journal entries to the actuals ledger.

See Chapter 23, “Using Entry Events in PeopleSoft General Ledger,” CorrectingEntry Event Journal Errors, page 488.

Note. If these are subsystem journals with entry events, the Journal Edit process bypasses the entry eventprocesses for these journals because they have already been entry event processed in the subsystem.

Creating Budget Adjustment Journal Entries Using theGLJEADJ Entry Event ProcessTo create and process an entry event journal that adjusts the Commitment Control budget.

1. Access the Create Journal Entries - Header page.

2. Select an actuals ledger group that linked to Commitment Control ledgers, and enter anyother information relevant to the journal entry transactions.

The ledger group in the predefined data is Recording.

3. Click the Commitment Control link.

4. Select one of the following Commitment Control amount types, and then click OK:

• Encumbrance

• Pre-Encumbrance

• Collected Revenue

5. Access the Create Journal Entries- Lines page, and select the entry event code forthe adjustment that you want to make.

Only the adjustment entry event codes are available for selection.

6. Enter values for Account, Alt. Acct., Amount, and other relevant fields in the journal line.

If the journal is a Commitment Control budget adjustment journal, the account and alternateaccount, if applicable, do not appear by default. You must enter the values.

7. SelectEdit Journal to save and edit the journal entry as well as initiate the BudgetProcessor if commitment control is enabled.

Note. The Journal Edit process does not run the Entry Event Processor process forbudget adjustment journals. You must run the Entry Event Processor process separatelyafter running the Budget Processor process.

8. Correct any entry event journal errors if they exist.



See Chapter 23, “Using Entry Events in PeopleSoft General Ledger,” CorrectingEntry Event Journal Errors, page 488.

9. Run the Entry Event processor from the Process Journals - Entry Event Journals page.

The processor updates or creates the accounting lines in the Adjustment Journal Accounting Line record.

Note. Budget adjustment journals are processed using the same model as accounts payable, purchasing, andaccounts receivable, where the entry event accounting transactions are written to a separate accounting linerecord and the journal is generated later. If a budget adjustment journal has been processed by the EntryEvent Processor process and subsequent changes are made to the journal, adjusting entries are created.

10. Select Subsystem Journals, Generate Journals to create budgetary accounting journalsfrom the adjustment journal accounting line record.

11. Select Process Journals, Edit Journals, Mark Journals for Posting, and Post Journals topost the journals to their appropriate ledgers.

Warning! If you change the Commitment Control amount type on the journal, the entry event lines arereversed for the previous amount type. For example, suppose that you select the Commitment Control amounttype Actuals and Recognized to create a journal and run the Journal Edit process to generate the entry eventlines then you realize that you intended to create a budget adjustment journal for an encumbrance instead. Ifyou attempt to select the Commitment Control amount type Encumbrance, the following message appears:

The CC Amount Type has been changed from ’Actuals and Recognized’ to ’Encumbrance’.

Because you changed the Commitment Control amount type, the entry event information that you enteredis no longer appropriate. If you select Cancel, the Commitment Control amount type remains Actualsand Recognized. If you select OK to accept the change, the original journal entry’s entry event codeswill be wiped out. When you enter the data and run the Journal Edit process for the new journal entry,any generated obsolete entry event lines are also deleted. Regardless of the Commitment Control amounttype that you select, the original entry event codes will be wiped out when you select OK.

Correcting Entry Event Journal ErrorsWhen you correct an entry events journal, the effect on the entry event lines dependson the type of error that occurs.


• Correct journal entry errors containing entry events with suspense option off.

• Correct journal entry errors containing entry events with suspense option on.

Correcting Journal Entry Errors Containing EntryEvents with Suspense Option OffTo correct an error in a journal line when the journal amount or ChartField is incorrectand the entry event was processed successfully:



1. Correct the error, such as an incorrect amount or ChartField selection, in the journal line.

2. Run the Journal Edit process.

The Journal Edit process edits the journal line; however, the Entry Event Processorprocess does not run again.

Correcting Journal Entry Errors Containing EntryEvents with Suspense Option OnTo correct errors for journals with entry events using suspense journal option, make sure that you indicateon the Journal Source - Journal Options page, the Ledgers For A Unit - Journal Edit Options page, or theGeneral Ledger - Journal Options page that you want the system to generate a suspense journal line foreach journal line with errors that can be suspended as well as the out-of-balance situation.

When you enter transactions with entry events that are set up to use suspense journals, if the original entryevent journal line contains an error, its amount is set to 0 and the system creates a suspense line that inherits theentry event code to support intra/interunit entry event process steps. However, Entry Event Processor skips toprocess the original entry event journal line as well as its edit suspense line. For non- intra/interunit journal,since the original entry event journal is out-of-balance, system also creates a balance suspense line. In a word,when a journal line with entry event goes to suspense, the entry event has no effect on this line.

The entry event field is a display-only field on the Journal Suspense Correction page. When you correctthe suspense journal using this page, be sure to correct the amount or ChartField error on the lines withentry event codes, and put the entry event offset account and other ChartFields on the balance suspenseline which doesn’t have the entry event code. When you run the Journal Edit process on the correctionjournal, the Entry Event Processor process does not run for this correction journal.

Note. If the error occurs when the entry event processor runs, the journal header status indicates that anerror occurred. This prevents processing of the journal until you resolve the entry event problem.

See Also

Chapter 10, “Processing Journals,” Correcting Journal Errors, page 210



PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Setting Up Ledgers,” Linking Ledgers to a Ledger Group

Chapter 18, “Reviewing Financial Information,” Reviewing Entry Event Accounting, page 419

Drilling Down to Entry Event AccountingYou can:

• Drill down to the entry event budget line details.

• Drill down to the entry event general ledger adjustment accounting line details.



See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Using Journal Generator,”Defining Journal Generator Template Defaults

Chapter 18, “Reviewing Financial Information,” Reviewing Entry Event Accounting, page 419


CHAPTER 24

Using OLAP Tools to Analyze General Ledger Data

This section provides an overview of using online analytical processing (OLAP) cubes withPeopleSoft General Ledger and discusses how to:

• Plan the OLAP database.

• Prepare trees and queries.

• Define the cube.

• Build the cube.

• Analyze cube data.

See Also

PeopleTools PeopleBook: PeopleSoft Cube Manager

Understanding OLAP CubesWhen you analyze PeopleSoft General Ledger data, you can look at it from several perspectives: by company,division or business unit, product line, or time. If you use the columns or rows on a typical spreadsheet toanalyze PeopleSoft data, it is difficult to represent more than two dimensions (or attributes) at a time.

The OLAP tools that integrate with PeopleSoft products offer a solution for viewing PeopleSoftdata with three or more dimensions. You can think of the OLAP tools as an arrangement of datain a cube, with each side of the cube representing a different dimension.

To view data from different perspectives, you can pivot or reposition the cube.

You can use different combinations of dimensions to slice and dice the data. For example, you couldexamine ledger balances for all Travel and Expense accounts in the Training department of the Westernregion for the entire year. You couldslice off part of the cube ordice it to access an individual cell,perhaps to view a single business unit. These multidimensional views of financial data can providevaluable information for effective data analysis, decision-making, and forecasting.

Before you set up PeopleSoft General Ledger for OLAP tools, you should be familiar with general OLAPconcepts and terminology, as well as the use of PeopleSoft Query, Tree Manager, and Cube Manager.

You use PeopleSoft Cube Manager to build multidimensional databases of information. CubeManager integrates with the following OLAP tools:

• Cognos PowerPlay

• Hyperion Essbase


Using OLAP Tools to Analyze General Ledger Data Chapter 24

• Generic Star Schema

PeopleTools comes with Cognos PowerPlay, which provides a standard OLAP cube template for usein PeopleSoft General Ledger. This makes it possible to design and build OLAP databases (referredto as cubes) for multidimensional analysis and reporting of general ledger data.

After the PeopleSoft General Ledger data is integrated with the third-party OLAP tool of yourchoice, you can use the OLAP tool to analyze and interact with data.

Note. All OLAP objects delivered with PeopleSoft General Ledger are for demonstration purpose only. Thisincludes queries, trees, dimensions, cube definitions, and GL specific run control pages. You must design yourOLAP objects according to your business needs and should use the delivered sample objects only as a reference.

Planning the OLAP DatabaseIntegrating OLAP tools with PeopleSoft General Ledger data begins with a careful examination ofthe data that you want to report on and analyze by using OLAP. You must define specific goalsand determine the results that you need from online data analysis.

Preparing Trees and QueriesAfter defining goals, you must design the PeopleSoft trees and queries that are appropriate for creatingboth the structure and data of the OLAP database (the cube) that you plan to build.

To map the ledger query result to the cube, each column of the query becomes either adimensionora measurefor the cube. For each dimension, you specify how detail values roll up to higher levels.For ChartFields, such as Department ID, you can use existing department trees for the roll-up, oryou can create additional trees or queries for use with OLAP. In addition, you must define a queryto extract the data from the PeopleSoft database and add it to the OLAP cube.

PeopleSoft General Ledger comes with the following queries and trees. You can usethem as delivered or modify them.

General Ledger Queries OLAP_LEDGER_ACT_01

OLAP_LEDGER_BUDG_01

OLAP_LEDGER_02

OLAP_ACCOUNT_FLIPSIGN

OLAP_ACCTREE_FLIPSIGN

General Ledger Trees ACCTROLLUP

PRODUCT

DEPARTMENTS

ACCOUNTING PERIOD


Chapter 24 Using OLAP Tools to Analyze General Ledger Data

Defining the CubeAfter you define the queries and trees to use with the cube, define the basic structure ofthe cube itself by using PeopleSoft Cube Manager.

Cube Manager links the data source (a query) and the dimensions of the OLAP cube that youare creating. You use Cube Manager to specify how dimension data should roll up by usingqueries, trees, or both queries and trees. As needed, you can reuse and easily modify the designof the dimensions, cube definition, and cube instance definitions.

To define the cube:

1. Define the dimensions of the cube.

Use the Dimension page and its related pages to begin building the structure of each dimensionthat comprises the cube. You define the sources, tree, query, (or both tree and query), andother settings for dimension data. You do not define any data for the cube at this point.You must create one entry for each dimension in the cube.

PeopleSoft delivers the following sample dimensions and you can use them asdelivered or modify them as needed:

• GL_ACCOUNT

• GL_ACCOUNT_RS

• DEPARTMENT_FUNC

• PRODUCT_MFG

• PERIOD

2. Create a cube definition that defines the basic structure of the cube.

Select the dimensions and measures that make up the cube and the data source queriesthat populate the members and cube cells with data. Like dimensions, cube definitionsare platform independent and can be reused.

PeopleSoft delivers the following sample cube definitions. You can use them asdelivered or modify them as needed.

• LEDGER_DETAIL

• LEDGER_VARIANCE

3. Create a cube instance definition.

A cube instance is the output of Cube Manager. It is a physical cube that is built by the Cube Builderprocess in PowerPlay, Essbase, OLAP Services, or PS/ROLAP. The definition of a cube instance createsthe link between the platform-independent definition of the cube and the actual physical storage mechanismof the cube. This step tells Cube Manager where to create the cube that you have defined.

PeopleSoft delivers the following sample cube instances. You can use them asdelivered or modify them as needed..

• LEDGER_DET_EB

• LEDGER_DET_PP



• LEDGER_VAR_01

Building the CubeThis section provides an overview of cube building and discusses how to build the aging analysis cube.

Understanding Cube BuildingTo build a cube, you have a choice of two pages, which run a background process that extractshierarchies and data from PeopleSoft General Ledger:

• The Build Cube Request page in Cube Manager (described in thePeopleSoft PeopleTools PeopleBook).

• The Build Ledger Cubes Request page in PeopleSoft General Ledger.

The Build Ledgers Cubes Request page runs the background process that creates ledger cubes. You can alsouse this page as a template for creating a specialized request page for a different type of cube.

Page Used to Build a General Ledger Cube


Build Ledger Cubes RequestGL_OLAP_LED_REQ General Ledger, GeneralReports, Build LedgerCubes, Build Ledger CubesRequest

Build an OLAP cube thatdisplays ledger informationor create a template forbuilding other cubes.

Building a Ledger CubeAccess the Build Ledger Cubes Request page.


Chapter 24 Using OLAP Tools to Analyze General Ledger Data

Build Ledger Cubes Request page

Cube Instance ID Select the cube template to build the cube.

Post-Build Script If you use Essbase, PowerPlay, OLAP Services, or PS/ROLAP, usethis field to indicate the script that you want to run on the cubeafter the system builds and populates it.

Ledger Select the ledger for which you are building this cube.

From andTo Fiscal Year The beginning and ending fiscal years for this cube.

From andTo Period The beginning and ending period for this cube.

Meta-Data Action The period over which an accumulator collects and accumulatesamounts. Select one of the following values:

Create:Create the cube. If a cube already exists, then Cube Manager recreatesit, overwriting any dimensions and data that previously existed.

None: Do not change the structure of the cube or its individualdimensions. (Use to update data only.)

Update: Update the structure of the cube according to the metadataupdate action. For PowerPlay, this has the same effect asCreate.This field value is linked to the Meta-Data Update Action field onthe Essbase Cube Instance Definition page.

Data Action The action that takes place when updating the cube. Selectone of the following values:

Create: Completely reload the data and overwrite any existing data.

None: Not applicable in PeopleSoft General Ledger.



Update: Update the existing data. For Essbase, this option is linkedto the data load action that is on the Essbase Cube Instance Definitionpage. This option does not apply to PowerPlay.

Analyzing Cube DataYou can use PowerPlay (or another third-party OLAP tool, depending on the template that you use) to view thecube from the various dimensions that you defined. You can look at the data in numerical or graphical format.

You can pivot, reposition, and manipulate the data and create graphs and charts.


CHAPTER 25

Federal Government, Statutory, and XBRLFinancial Statement Reporting

This chapter provides an overview of various federal government, statutory, andXBRL reporting and discusses how to:

• Set up FACTS I data.

• Set up FACTS I trees.

• Process and generate a FACTS I flat file.

• Set up FACTS II data.

• Create FACTS II trees.

• Process and generate a FACTS II flat file.

• Define, generate, create, and print SF224, SF1219, and SF1220 reports.

• Define and generate the Fund Balance Reconciliation report.

• Configure the FUND_STATUS.xnv PeopleSoft/nVision Report

• Set up federal reimbursable agreement accounts in GL.

• Use XBRL to Produce Balance Sheets and Income Statements.

• Set up regulatory ledger report data.

• Create a regulatory ledger file and reports.

Understanding Federal Government, Statutory,and XBRL Reporting

This section presents an overview of :

• PeopleSoft federal government reporting.

• PeopleSoft statutory reporting

• PeopleSoft XBRL financial statement reporting.

PeopleSoft Federal Government ReportingFederal agencies can produce these reports:


Federal Government, Statutory, and XBRL Financial Statement Reporting Chapter 25

• FACTS I reports

- FACTS I Validation Report — GLS8310

This report is generated when you run the FACTS I Validation process. It describes any outstandingissues for each FACTS I edit that is run for your FACTS I accumulated data.

- FACTS I Online Trial Balance — GLS8311

This report displays the status of the General Ledger account balances along with thecorresponding USSGL account attributes based on each Treasury Symbol. The data forthis report is based on the FACTS I staging tables.

• FACTS II reports

- FACTS II Validation Report — GLS8303

This report is generated when you run the FACTS II Validation process. It describes any outstandingissues for each FACTS II edit that is run for your FACTS II accumulated data.

- Ledger with Attributes report — GLS7017

This report that lists:

- FACTS II Online Trial Balance — GLS8312

This report enables you to view the status of the General Ledger account balances alongwith the corresponding USSGL account attributes for a specific accounting period. The datafor this report is based on the FACTS II staging tables.

• Federal Transaction Register — GLS8501

This is an online report that displays values at the fund, department, and TAS/TAFS levels for eachaccounting period along with each ChartField’s attributes and attribute values.

• Federal Trial Balance —GLS8500

• Reconciliation by Source Report — GLS5001

• Reconciliation by ChartField — GLS5005

• Fund Balance Reconciliation Report — GLS9500

Run this report following the Fund Balance Reconciliation process, which compares account activityand trial balance data imported from the U.S. Treasury to a federal agency’s cash activity. It containsthe differences between a federal agency’s data and the U.S. Treasury’s data.

• SF224 — Statement of Cash Transactions report

This is a monthly report sent to the U.S. Treasury that identifies the dollar amounts of confirmed U.S.disbursements and collections for an agency by Agency Location Code and fiscal month. This report is used toensure agreement between the agency’s records of disbursement and collections and those of the U.S. Treasury.

- SF224 — Statement of Cash Transaction Detail report

- This report includes the detail transactions that make up the totals on the SF224 — Statement ofCash Transactions report and may be used internally for reconciliation purposes.

• SF1219 — Statement of Accountability report


Chapter 25 Federal Government, Statutory, and XBRL Financial Statement Reporting

This report is used to determine the accountability of disbursing officers for funds held outsidethe Department of Treasury (cash on hand) by U.S. Treasury Regional Finance Centers (RFCs)and other nonmilitary agencies that do not do their own disbursing.

• SF1220 — Statement of Transactions According to Appropriations, Funds, and Receipt Amounts.

This report provides the U.S. Treasury with a monthly statement of payments and collectionsperformed by departments and agencies that do their own disbursing.

• SF132 Apportionment and Reapportionment Schedule Report

This report defines the apportionment and reapportionment of each appropriation or fund accountthat is subject to apportionment. PeopleSoft provides a template that enables government to designPSnVision reports that adhere to the guidelines for this report. This report can be prepared andprinted for submission to the Office of Management and Budget (OMB).

• SF133 Quarterly Report on Budget Execution and Budgetary Resources

This report defines whether the budgetary resources are available for obligations, whether thebudgetary resources have been obligated, and, if obligated, whether the obligated amounts have beenspent. PeopleSoft provides a template that enables government to design PSnVision reports thatadhere to the guidelines for these reports. This report is available in hard copy.

• Federal Agency Financial Statements

Federal agencies must submit these financial statements to congress and the Office of Managementand Budget (OMB). PeopleSoft designed templates to work with PSnVision that can be modified tocreate these financial statements based on your agency’s requirements.

- Balance Sheet presents, as of a specific time, the amounts of future economic benefits owned or managedby the reporting entity exclusive of items subject to stewardship reporting (assets), amounts owedby the entity (liabilities), and amounts which compromise the difference (net position).

- Statement of Net Cost reports the gross cost incurred by the reporting agency less anyexchange revenue earned from its activities.

- Statement of Changes in Net Position reports the changes in net position for the reportingperiod. Net position is affected by changes in two components, cumulative resultsof operations and unexpended appropriations.

- Statement of Budgetary Resources reports how budgetary resources were made available,as well as their status at the end of the period.

- Statement of Financing reports the relationship between net obligations derived from an entity’sbudgetary accounts and net cost of operations derived from an entity’s proprietary accounts byidentifying and explaining key differences between the two accounts.

- Statement of Custodial Activity is required for agencies that collect non-exchange revenue for the GeneralFund of the Treasury, a trust fund, or other recipient activities. The collecting agencies do not recognizeas revenue those collections that have been or should be transferred as revenue to others. Rather, theyaccount for sources and disposition of the collections as custodial activity on this statement.

• FUND_STATUS PeopleSoft/nVision Report



The United States Federal Government must comply with the Antideficiency Act, which prohibitsany Federal employee from entering into contracts that exceed the enacted appropriationsfor the year or purchasing services and merchandise before appropriations are enacted. Thisreport provides funding information for informed management decisions. This is an nVisiontemplate that can be modified for your agency’s requirements.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Configuring the FUND_STATUS PS/nVision Report, page 581.

• Federal Reimbursable Agreements

Federal agencies and the Department of Defense (DOD) often use reimbursable funding to performwork on behalf of others and then be reimbursed for the work. A reimbursement ID is createdbased upon an agreement between agencies or an outside organization. This agreement is negotiatedprior to acceptance. Agencies may only bill back the pre-negotiated reimbursable amount, whichmakes it imperative that they are able to track reimbursable agreements separately from other typesof funding, as well as access the current status of the reimbursable amount, billing limit, amountexpended against the agreement, and the amounts collected against the agreement.

Note. Navigation paths, descriptions, and examples of most of these reports are inGeneral Ledger Appendix A: Reports.

PeopleSoft Statutory ReportingThe Government Accounting Standards Board (GASB) 34 /35 requires state and local governments,and public colleges and universities to submit basic financial statements. PeopleSoft provides atemplate that enables local and state governments and public colleges and universities to designPSnVision reports that adhere to the GASB 34/35 guidelines.

PeopleSoft XBRL Financial Statement ReportingXBRL is a royalty-free, open specification software that uses XML data tags to prepare and publishinformation. It is particularly appropriate to the presentation of financial reports on the Internetand across software products. XBRL reports also reduce the risk of data entry error by eliminatingthe need to manually key information for different venues and formats.

PeopleSoft enables you to create balance sheets and income statements in XBRL that conformsto the XBRL schema and taxonomies for US GAAP.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,” UsingXBRL to Produce Balance Sheets and Income Statements, page 588.

Setting Up FACTS I DataTo set up FACTS I data, use the following components:

• ChartField Attributes (CF_ATTRIBUTES)


• Fund Code (FUND_DEFINITION)



• Miscellaneous ChartFields (F2_ELEMENT_CF)

Use the FUND_CF component interface to load data into the tables for the Fund Code component. Use theACCOUNT_CF component interface to load data into the tables for the Account component.


• Set up FACTS I ChartField attributes.

• Set up Miscellaneous ChartFields for Federal or Non Federal Partner & Transfer Agency.

Note. Setup of Miscellaneous ChartFields applies to both FACTS I and FACTS II.

See Also

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,” UsingXBRL to Produce Balance Sheets and Income Statements, page 588

PeopleTools PeopleBooks: PeopleSoft Tree Manager, “Using Tree Manager”

Understanding FACTS I ReportingFACTS I is a federal government electronic reporting feature that federal government agencies use toreport the proprietary account balances of the agency, including assets, liabilities, net position, revenues,and expenses in a pre-closing Adjusted Trial Balance (ATB) format. Agencies submit this data to the U.S.Treasury in flat file format for preparation of the U.S. Audited Consolidated Financial Statements. TheATB is a list of Standard General Ledger (SGL) accounts in numerical order with pre-closing adjustedbalances that are prepared on a specified date and are transmitted by fund group. The total sum of thedebit balances must equal the total sum of the credit balances in an ATB. These account balances mayinclude both governmental and non-governmental totals and are normally stated separately.

Overview of FACTS I Setup

After setting up your US SGL Account ChartFields, Fund Code ChartFields, and any other ChartFieldsused by your agency, FACTS I requires that you set up and associate these ChartField attributeswith your accounts and fund codes, as well as miscellaneous ChartFields:

• Exchange ChartField Attribute — Account ChartField

• Custodial ChartField Attribute — Account ChartField

• Budget Subfunction Attribute — Fund Code ChartField

The FACTS I ChartFields are determined during implementation .

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up FACTS I Data, page 500.

Overview of FACTS I Trees

You also must set up FACTS I trees. These trees determine how the posting level ChartField values roll up tothe detail values mandated by the U.S. Treasury for FACTS I reporting. After you set up your FACTS I trees,you add them to a FACTS tree group. When you are ready to process your FACTS I data, you identify thisFACTS tree group on the Generate FACTS I, Validation Report, and Trial Balance page. The FACTS I trees are:

• Transfer Agency Tree (Common to FACTS I and FACTS II)



This tree consists of transfer agency levels that contain associated Transfer Agency ChartField rangeswhere the sum of the accounts roll up into a total amount for each transfer agency to report. Note thatthe Transfer Agency chartfield is specified on the Miscellaneous ChartFields page under FACTS IIDefinition. The totals for each transfer agency can also roll up into a total for all the agencies andtheir associated accounts at a summary level for reporting purposes. The level that displays for thistree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Bureau tree.

This tree consists of a hierarchy of bureau levels with the ledger values that roll up into them. The level thatdisplays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Department tree.

This tree consists of a hierarchy of department levels with the ledger values that roll up into them. The levelthat displays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Fund Group tree.

This tree consists of Fund Group levels with the fund ChartField values that roll up into them. All of thesefund group levels and associated fund values roll up to a summary level for reporting purposes. The levelthat displays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Account tree.

This tree consists of levels of Account Types (Assets, Liabilities, etc.) where the totals of associated AccountChartField values roll up into one total at for each level, which in turn can roll up into a larger total. The levelthat displays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Exchange/Account tree.

This tree is used to perform the FACTS I validation edits 30–33. The tree identifiesaccounts that require the Exchange attribute value.

• Custodial/Account tree.

This tree is used to perform the FACTS I validation edits 40–43. The tree identifiesaccounts that require the Custodial attribute value.

• Budget SubFunction/Account tree.

This tree is used to perform the FACTS I validation edits 52 and 53. The tree identifiesaccounts that require the Budget Subfunction attribute value.

• FACTS I Transaction Partner tree.

This tree has levels that represent the categories of transaction partners (federal (F) and non-federal (N) andthe breakdown of those categories such as X for Non-Federal and E for Non-Federal Exception. The levelthat displays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

• Transaction Partner/Account tree.

This tree is used to perform the FACTS I validation edits 20–23. The tree identifies accountsthat require the Transaction Partner attribute value.

• Accts. Req. Attributes (accounts requiring attributes) tree.

The levels of this tree indicate the U.S. Treasury attributes required for FACTS I and their associated accounts.



Note. The use of the FACTS I Trading Partner tree is basically equivalent to the useof the FACTS II Transfer Agency tree.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up FACTS I Trees, page 506.

Overview of FACTS I Processing

After you set up your data and trees, perform these steps to load the Master Appropriation File(MAF) data and generate a FACTS I flat file to send to the U.S. Treasury.

1. Import the U.S. Treasury MAF, FACTS I SGL account, and Trading Partner data.

2. Run the GL_FACTS I application engine to:

• Generate and store the FACTS I data.

• Validate the generated FACTS I data and note any errors.

• Create the FACTS I flat file, provided the validation is error free.

3. Print the FACTS I Validation report.

4. If necessary, correct any validation errors and repeat the cycle until the validation is error free.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up and Generating a FACTS I Flat File, page 522.

PrerequisitesBefore setting up FACTS I data or regulatory reporting data, complete the these procedures:

• Set up FACTS I business units.

• Set up FACTS I SGL accounts

• Define ChartFields

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Defining and Using ChartFields,”Defining and Using Account Types and Attributes



Pages Used to Set Up FACTS I Data


ChartField Attributes CF_ATTRIBUTES Set Up Financials/SupplyChain, Common Definitions,Design ChartFields,Configure, Attributes,ChartField Attributes

Enter the ChartFieldattributes and attributevalues listed on theAttributes Table.

Account GL_ACCOUNT Set Up Financials/SupplyChain, Common Definitions,Design ChartFields, DefineValues, ChartField Values,Account

Access the AccountChartField that you wantto associate with selectedACCOUNT ChartFieldattributes on the ChartFieldAttributes page.

Fund Code FUND_DEFINITION Set Up Financials/SupplyChain, Common Definitions,Design ChartFields, DefineValues, ChartField Values,Fund Code

Access the Fund CodeChartField that you wantto associate with selectedFUND_CODE ChartFieldattributes.

ChartField Attributes CF_ATTRIB_VALUES Click the Attributes link onthe Account or Fund CodeChartField pages.

Select a ChartField attributeand attribute value thatapplies to either the selectedFund Group or selectedAccount ChartField.

Miscellaneous ChartFields F2_ELEMENT_CF1 General Ledger, FederalReports, FACTS II,Miscellaneous ChartFields

Set up ChartFields forCategory B Program, CohortYear, Federal or NonFederalPartner, Transfer Account,and Transfer Agency.

Setting Up FACTS I ChartField AttributesThere are two account attributes and one fund code attribute in the following table. You can use thepredefined data that PeopleSoft provides in the sample database as a guide to set up your ChartFieldattributes and link them to your agency’s appropriate accounts and fund codes.

Access the ChartField Attributes page.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up FACTS I ChartField Attributes, page 504.



Field NameChartField

Attribute Name DescriptionAllow Multiple

Values

ChartFieldAttribute Value(Description)

ACCOUNT EXCHANGE Indicates whetherthe revenuebalance reported isexchange revenueor non-exchangerevenue.

N

Warning! This fieldshould always be N.

X (ExchangeRevenue)

T (NonexchangeRevenue)

ACCOUNT CUSTODIAL Indicates whetherthe reportedbalance iscustodial ornon-custodialand reported bythe agency ina Statement ofCustodial Activityor in a separatefootnote of acustodial activity.

N

Warning! This fieldshould always be N.

S (Custodial)

A (Noncustodial)

FUND_CODE BUDGET_SUBFUNC

Subfunctionsused in theclassification ofdata according tomajor purposeserved (forexample, income,security ornational defense).

N

Warning! This fieldshould always be N

Three-digitbudget functionalclassificationsubfunction. Each3-digit budgetsubfunction codecontained in theMAF represents asubfunction groupedunder one of 19functions.

See Also

PeopleSoft PeopleTools PeopleBooks: “PeopleSoft Tree Manager,” Creating Trees

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise ServiceAutomation, and Supply Chain Management PeopleBook, “Summarizing ChartFields UsingTrees,” Understanding ChartField Summarization with Trees

Specifying Miscellaneous ChartFields for FACTS IThe two fields that you set up for FACTS I in Miscellaneous ChartFields are Federal or Non Federal Partnerand Transfer Agency. The setup of these two fields applies to both FACTS I and FACTS II.

You can change delivered ChartField specifications to any configurable ChartField. For example, you canassociate the FACTS I Data Element Transfer Agency with ChartField 2 or any of the configurable ChartFields.

Access the Miscellaneous ChartField page.



See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Specifying Miscellaneous ChartFields, page 544.

Setting Up FACTS I TreesTo set up FACTS I trees, use the following components:

• Tree Manager (PSTREEMGR)

• FACTS Tree Group (FACTS_TREE_GRP)

• TableSet Control (SET_CNTRL_TABLE1)


• Set up a FACTS Transfer Agency tree.

• Set up a FACTS I Bureau tree.

• Set up a FACTS I Fund Group tree.

• Set up a FACTS I Department tree.

• Set up a FACTS I Account tree.

• Set up a FACTS I Exchange/Acct. (account) tree.

• Set up a FACTS I Custodial/Acct. (account) tree.

• Set up a FACTS I Budget Subfunction/Acct. (account) tree.

• Set up a FACTS I Transaction Partner tree.

• Set up a FACTS I Transaction Partner/Acct. (account) tree.

• Set up a FACTS I Accts. Req Attributes (accounts requiring attributes) tree.

• Set up a FACTS I Tree Group.

• Configure TablesSet Control for FACTS I processing.

• Configure TableSet Control record group data.

• Configure TableSet Control trees.



Pages Used to Set Up FACTS I Trees


Tree Definition andProperties

PSTREEDEFN Tree Manager, TreeManager, Create New Tree

Enter a tree name and clickthe Add button.

Create a new tree to identifythe tree name, relatedstructure ID, setID, and anyother rules or characteristicsof the tree.

Tree Manager PSTREEMGR Tree Manager, TreeManager, Create New Tree

Access an existing tree withoptions that enable you toaccess and modify the treedefinition and properties,print, and configure treedisplay options.

FACTS Tree Group FACTS_TREE_GRP General Ledger, FederalReports, FACTS Tree Group

Contains all of the FACTS Itrees and the roll-up level.This page is identified on therun control page for FACTSI reporting and processing.

TableSet Control - RecordGroup

SET_CNTRL_TABLE1 PeopleTools, Utilities,Administration, TableSetControl, Record Group

Defines all the recordgroups based on a specificSet Control Value and theirassociated setIDs. Alsoidentifies the default setIDof the General Ledgerbusiness unit.

TableSet Control - Tree SET_CNTRL_TABLE2 PeopleTools, Utilities,Administration, TableSetControl, Tree

Set up tree values on thistable if your setID for yourbusiness units do not matchyour default setID.

See Also

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up FACTS I Data, page 500

Setting Up a FACTS I (FACTS II) Transfer Agency TreeCreate the Transfer Agency tree using PeopleSoft Tree Manger based on this example.

This tree contains nodes for each of the transfer agencies and is used by both FACTS I and FACTSII. If you have decided to use the same ChartField for both Transfer Agency and Transfer Account,then the values in your ledger for that ChartField will represent both Transfer Agency and TransferAccount at the same time. The tree will allow the program to translate the ledger’s combination TransferAgency/Account value to the Transfer Agency value required by US Treasury.



FACTS Transfer Agency Tree

Setting Up a FACTS I Bureau TreeCreate a FACTS I Bureau tree for your organization in PeopleSoft Tree Manager similar to this example.



FACTS I Bureau Tree

The node values at one level of the tree represent the values that the U.S. Treasury is expecting in theFACTS I flat file. This is the level that you select on the FACTS Tree Group page.

See Also

PeopleSoft PeopleTools PeopleBook: “PeopleSoft Tree Manager,” Introduction toTree Manager and Creating Trees


Setting Up a FACTS I Fund Group TreeSet up a Fund Group tree for your organization using PeopleSoft Tree Manager similar to this example.



FACTS I Fund Group Tree

See Also

PeopleTools PeopleBook: “PeopleSoft Tree Manager”

Setting Up a FACTS I Department TreeSet up a Department tree for your organization using PeopleSoft Tree Manager similar to this example.



FACTS I Department Tree

This tree consists of a hierarchy of department levels with the ledger values that roll up into them. The levelthat displays for this tree on the FACTS Tree Group page indicates the level that will be used for reporting.

See Also


Setting Up a FACTS I Account TreeSet up an Account tree for your organization using PeopleSoft Tree Manager similar to this example.



FACTS I Account Tree

For FACTS I reporting, the Account value is 4-characters; the node value is 1000 at theACCDT_TYPE level in the FACTS_ACCOUNT tree

See Also


Setting Up a FACTS I Exchange/ Acct TreeSet up the Exchange/Account tree using PeopleSoft Tree Manager similar to this example.



Note. The FACTS I Exchange/ Acct tree requires three nodes: T, X, and X OR T. Thenode names must be named exactly as specified.

FACTS I Exchange Account Tree

See Also

PeopleTools PeopleBook: “People Soft Tree Manager”

Setting Up a FACTS I Custodial/ Acct TreeSet up the Custodial/Acct tree using PeopleSoft Tree Manager similar to this example.

Note. The FACTS I Custodial/ Acct tree requires three nodes: S, A, and S OR A. Thenode names must be named exactly as specified.



FACTS I Custodial/Acct Tree

See Also


Setting Up a FACTS I Budget Subfunction/ Acct TreeSet up the Budget Subfunction tree using PeopleSoft Tree Manager similar to this example.

Note. The FACTS I Budget Sunfunction/ Acct tree requires no specific node name. This treeonly has to list those accounts that require this attribute to be reported.



FACTS I Budget Subfunction/ Acct Tree

See Also


Setting Up a FACTS I/II Transaction Partner TreeSet up the FACTS I Tran Partner tree using PeopleSoft Tree Manager similar to this example.



FACTS I/II Transaction Partner Tree

See Also


Setting Up a FACTS I Transaction Partner/ AcctTreeSet up the Transaction Partner/Acct. tree using PeopleSoft Tree Manager similar to this example.

Note. The FACTS I Transaction Partner/ Acct tree requires three nodes: N, F, and N ORF. The node names must be named exactly as specified.



FACTS I Transaction Partner/Acct Tree

See Also


Setting Up a FACTS I Accounts Requiring Attributes TreeSet up the FACTS I Accounts Req Attributes tree using PeopleSoft Tree Manager similar to this example.



FACTS I Accts Req Attributes (accounts requiring attributes) Tree

Note. The FACTS I Account Req Attributes tree differs from the FACTS II tree of the samename in that it only requires three nodes: TRADING_ PARTNER, FED_NONFED, andBUDGET_SUBFUNC. The node names must be named exactly as specified.

See Also

PeopeTools PeopleBook: PeopleSoft Tree Manager

Creating a Tree Group for FACTS IAccess the FACTS Tree Group page.



FACTS Tree Group - FACTS I and FACTS II Trees and Tree Levels

Common Trees and TreeLevels

Select the Transfer Agency Tree name and the Tree Level thatyou created foryour organization. This tree is used by both FACTS I and FACTS II.

FACTS I Trees and TreeLevels

Associate the appropriate tree names and the tree levels that youcreated for your organization with each of the PeopleSoft treenames. These are FACTS I trees only.

FACTS II Trees andTree Levels

Associate the appropriate tree names and the tree levels that youcreated for your organization with each of the PeopleSoft treenames. These are FACTS II trees only.



Configuring TableSet Control for FACTS I ProcessingYou should carefully choose the setIDs used for the FACTS Tree Group and the FACTS I Trees and configurethe TableSet Control setIDs accordingly. Incorrect configuration could result in the unavailability of tree groupnames or tree names in prompt lists on pages, or in the inability of the FACTS I process to retrieve data.

If you have only one business unit in your organization and use only one setID to set up yourChartFields, trees, and tree groups, Tree Groups, then your TablesSet Control setIDs should all bethe same and do not need changing. Also, if you use more than one business unit that uses the samedefault setID, then the Control Tables should not need to be modified. However, check the TableSetControl pages for each business unit and setID, using their values as the Set Control Values, to ensurethat all tables and trees are using the same setID. Note that the Tree Group table is in the new GL_15Federal Reports Record Group in the TableSet Control Record Group page.

If you use more than one SetID in your organization for setting up your ChartFields, trees, and treegroups, then you must make sure each setID that you use is set up correctly in TableSet Controls.The setIDs used in the following steps or chart are only examples.

1. Set up your FACTS I ChartFields, trees, and tree group using the FEDRL SetID.

2. Identify the general ledger business unit (for example, FED01) that you want to use for FACTS Iprocessing. Access the SetControl Value (FED01) in TableSet Control. The Default SetID on the TableSetControl Record Group page is the default setID that you set up for the general ledger business unit.

3. Find the GL_15 Federal Reports Record Group and select the setID (FEDRL) for GL_15 tomatch the setID (FEDRL) that you used to create your tree group.

The FACTS Tree Group table is a part of the GL_15 Record Group and must have the samesetID. This step enables the Tree Group dropdown list to appear on the Accumulate FACTS IData page so that you can select a FACTS Tree Group to process.

4. Is the Default SetID (SHARE) on the TableSet Control Record Group page the same as thesetID that you used to set up your trees? YES or NO?

The FACTS I processes normally refer to the Default SetID in the TableSet Control RecordGroup page and uses the default setIDs to retrieve the FACTS I tree.

5. If YES, you can save and exit TableSet Control.

6. If NO, you must enter each tree on the TableSet Control – Tree page that has a setID that is differentfrom the Default SetID on the TableSet Control – Record Group page.

7. If you run FACTS I processing on multiple business unit, repeat these steps.

Configuring TableSet Control Records Groups for FACTS IAccess the Record Group page.



TableSet Control - Record Group page

Set Control Value To run the FACTS II Accumulation and Validation processes, you mustenter a business unit. The business unit you use is theSet ControlValue that you select to ensure that the FACTS II tree group and treesare accessible during FACTS II processing.

Default SetID This is the Default SetID for the general ledger business unit that you enteredas your Set Control Value and that you intend to use for processing FACTS II.

Record Group ID andDescription

Find the Record Group ID,GL_15 Federal Reports. This recordgroup contains the FACTS Tree Group table.

SetID Select a SetID for this record group that matches the setID that you used to setup the FACTS Tree Group to use in the Accumulate FACTS I Data process.

The selected SetID enables you to display a list of FACTS Tree Groupsand select the Tree Group name in the Accumulate FACTS Data pagethat you want the FACTS I process to access.

Note. You do not need to change anything on either of the TableSetControl pages if you use only one SetID as the default for the businessunit that you intend to use for FACTS I processing and for setting upyour FACTS I ChartFields, trees and tree group.



Configuring TableSet Control Trees for FACTS IAccess the TableSet Control - Tree page.

TableSet Control Tree page

Setting Up and Generating a FACTS I Flat FileThis section discusses how to:

• Load MAF and FACTS I Data

• Review FACTS I MAF data.

• Set up and generate a FACTS I flat file.



Page Used to Generate a FACTS I Flat File


Load Facts I Data RUN_FACTSI_MAF General Ledger, FederalReports, FACTS I, LoadFacts I Data

Loads MAF data, SGLAccounts, or Trading Partnerdata into the PeopleSoftGeneral Ledger databases.

Review FACTS I MAF REVIEW_FACTSI_MAF General Ledger, FederalReports, FACTS I, ReviewFACTS I MAF

Review data for a selectedATB Treasury MAF file.

Generate FACTS I File,Validation Report andTrial Balance

RUN_CNTL_FACTSI General Ledger, FederalReports, FACTS I, FACTS IValidation and Trial Balance,Generate FACTS I File,Validation Report and TrialBalance

Select the criteria that arenecessary for PeopleSoftApplication Engine togenerate a FACTS I flatfile to upload to the U.S.Treasury’s GovernmentOn-line Accounting LinkSystem (GOALS), runa FACTS I ValidationReport and a FACTS I TrialBalance.

Process Scheduler RequestPRCSRQSTDLG General Ledger, FederalReports, FACTS I, FACTS IValidation and Trial Balance,Generate FACTS I File,Validation Report and TrialBalance, click Run.

Runs the GLFACTSI_MAFApplication Engine process.

Loading MAF and FACTS I DataAccess the Load FACTS I Data page:

Load FACTS I Data

FACTS I MAF, SGLAccounts, Trading Partners

Select one of these options to load the FACTS I MAF, SGL Accounts, orTrading Partner data from a file sent by the US Treasury to PeopleSoft General



Ledger. This data is loaded into database tables for later use when running thevalidation. These files are available for download from the US Treasury.

Attached File Enter the location of the selected file, for example: C:\temp\<filename>

Run Select Run to access the Process Scheduler Request page and run theGL_FACTSIMAF Application Engine process.

Click to attach the FACTS I file that you want to load.

Click the Delete Attachment button to delete the attached file in theAttached File field. This only deletes the file attachment. If you havealready clicked the Run button to upload the file, clicking this buttondoes not delete the data from the database table.

Click to open and review the contents of an attached FACTS I file.

Reviewing FACTS I MAF DataAccess the Review FACTS I MAF page.

Review FACTS I MAF

ATB Code Select a Treasury code that is associated with a MAF file.

Department Select if you want to narrow your search to MAF data for a specific department.

Bureau Select if you want to narrow your search to MAF data for a specific bureau.

Fund Group Select if you want to narrow your search to MAF data for a specific fund group.



Change Status Select one of these values:

• Add

• Change

• Delete

• No Change

Review Status Select one of these values:

• Disapprove

• In Process

• Review

• Submitted

Click this button after you enter the FACTS I MAF criteria.

Setting Up and Generating a FACTS I Flat FileAccess the Generate FACTS I File, Validation Report and Trial Balance page.

Generate FACTS I File, Validation Report and Trial Balance page

Language Select the language for this FACTS I report (only if the languageis other than English).

Business Unit Select the business unit.



Ledger Select the ledger that applies to this report and is associatedwith this business unit.

Fiscal Year Enter the fiscal year that applies to this FACTS I report.

From Period andTo Period Enter the begin and end accounting period range that applies to thisFACTS I report. These fields are required.

FACTS Tree Group Select the FACTS Tree Group associated with your FACTSI trees and tree levels.

Adjustment Period Select the adjustment periods to include in the output file and select theInclude Adjustments check box below. You can add more than one row.

Include Adjustments Select to include adjustment amounts in the output file.

Balance Forward Select to include beginning balances in the output file.


Select to include any adjustment made during closing in the output file.

Treasury Symbol Attribute Select the Treasury Symbol attributes to include in the output file.

Setting Up FACTS II DataTo set up FACTS II data, use the following components:

• Contact Information (F2_CONTACT)

• ChartField Attributes (CF_ATTRIBUTES)

• Fund Code (FUND_DEFINITION)


• Miscellaneous ChartFields (F2_ELEMENT_CF)

• FACTS II Attribute Cross Reference (F2_ATTRIB_XREF)

• Treasury Symbol Cross Ref (F2_TSYM_XREF)

Use the FUND_CF component interface to load data into the tables for the Fund Code component. Use theACCOUNT_CF component interface to load data into the tables for the Account component.


• Enter the FACTS II contact information.

• Create the preparer file.

• Process the FACTS II preparer file.

• Set up ChartField attributes.

• Link ChartField attributes to Fund Code and Account ChartFields.

• Specify Miscellaneous ChartFields.



• Set up ChartField attribute cross-references.

• Load MAF data.

• Review MAF file.

• Set up the FACTS II Treasury Symbol cross-references.

Understanding FACTS II ReportingFACTS II is a federal government electronic reporting of budgetary account data for quarterlyreporting to the U.S. Treasury and must meet these requirements:

• Record financial transactions with the required attributes.

• Import the U.S. Treasury MAF File for use in FACTS II processing.

• Accumulate fund, account, and other relevant data.

• Perform accounting edits on the FACTS II input files.

• Produce a FACTS II Accounting Edit Validation report.

• Generate a FACTS II flat file to send to the U.S. Treasury as input to the Government On-LineAccounting Link Information Access System (GOALS).

Note. FACTS I is a separate feature that produces proprietary accounting data in theFACTS I file format for the U.S. Treasury.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”PeopleSoft Federal Government Reporting, page 497.

Overview of FACTS II Setup

These steps outline the setup of FACTS II data:

1. Enter the FACTS II contact data.

2. Create the preparer file and send it to the U.S. Treasury.

3. Set up the Account and Fund Code ChartField attributes and attribute values.

4. Associate the appropriate attribute values with the Fund Code and Account ChartField values.

5. Specify the Miscellaneous ChartFields for Category B Program, Cohort Year, Federal orNon-Federal Partner, Transfer Account, and Transfer Agency.

6. Set up the attribute cross-reference data.

7. Review your ChartField attributes for accuracy.

8. Load the Master Account File (MAF) data obtained from the U.S. Treasury.

9. Review the MAF data containing Treasury Symbols.

10. Set up the Treasury Symbol cross reference data.

Overview of FACTS II Trees

You must set up these FACTS II trees and a FACTS tree group:



1. FACTS II Acct Rollup tree.

This tree enables an agency’s posting accounts to roll up to the SGL account structurerequired for FACTS II reporting.

2. FACTS II Cohort Year tree.

This tree enables any agency’s cohort year ChartField values to roll up to a cohortyear structure for FACTS II reporting.

3. FACTS II Category B tree.

This tree represents the Category Program ChartField values , and the 3 digit program sequence numberand the Category B program descriptions required by the FACTS II Treasury input file.

4. Accounts Requiring Attributes tree.

This tree represents the U.S. Treasury attributes and their associated accounts.

5. Transfer Agency tree.

This tree represents the U.S. Treasury department’s two-digit federal transfer agency codesand the ledger values that are translated to these codes.

6. Transfer Account tree.

This tree is represents the Treasury department’s four-digit federal transfer account codesand the ledger values that are translated to these codes.

7. Transaction Partner tree.

This tree represents the three types of transaction partners, Federal, Non Federal, and NonFederal Exceptions that are translated to these codes.

8. Set up the FACTS tree group using these tree names and levels.

Overview of FACTS II Processing

These steps are used to generate and process FACTS II data.

1. Run the GLS8302 process to accumulate the FACTS II data.

2. Review the accumulated FACTS II data for accuracy.

3. Run the GLS8303 process to validate the FACTS II data.

4. Review the validation results and, if necessary, correct configuration or other data,and repeat steps 1 through 3.

5. Create the FACTS II flat file to send to the U.S. Treasury.

6. Run GLS7017 Ledger with Attributes Report to verify the accuracy of the data.

7. Send FACTS II file to the U.S. Treasury.

Note. These rules are defined in the U.S. Treasury’s SGL Account Attributes Required for FACTS IIReporting of Detailed Financial Information in the U.S. Treasury’s website.

PrerequisitesBefore setting up FACTS II data or regulatory reporting data, complete these procedures:



• Set up FACTS II business units.

• Set up FACTS II SGL accounts

• Define ChartFields

See Also


Pages Used to Set Up FACTS II Data


FACTS II ContactInformation

F2_CONTACT_INFO General Ledger, FederalReports, FACTS IIDefinition, FACTS IIContact, FACTS II ContactInformation

Contains contactinformation about theperson(s) responsible forpreparing and certifyingFACTS II data for eachof the Appropriationsand sending it to the U.S.Treasury in the PreparerFile. Only preparers maychange an Appropriationsymbol’s SGL accounts orother related information.

Create Preparer File F2_RUN_CONTACT General Ledger, FederalReports, FACTS II Creation,Create Preparer File

Runs the Application EngineGL_F2 CONTACT,which creates the ContactInformation Record andContact Information RecordTrailer (Input) record inthe indicated input file andcreates an output flat file tosend to the U.S. Treasury.

Process Scheduler RequestPRCSRQSTDLG Click the Run button on theCreate Preparer page.

Runs the Create FACTSPreparer File (GL_F2CONTACT) process.

ChartField Attributes CF_ATTRIBUTES Set Up Financials/SupplyChain, Common Definitions,Design ChartFields,Configure, Attributes,ChartField Attributes

Enter the Fund Code andAccount ChartFieldattributes and attributevalues.

Fund Code FUND_DEFINITION Set Up Financials/SupplyChain, Common Definitions,Design ChartFields, DefineValues, ChartField Values,Fund Code

Access the Fund CodeChartField to associate withFUND_CODE ChartFieldattributes.

Account GL_ACCOUNT Set Up Financials/SupplyChain, Common Definitions,Design ChartFields, DefineValues, ChartField Values,Account

Access the AccountChartField to associate withACCOUNT ChartFieldattributes.



Page Name Object Name Navigation UsageChartField Attributes CF_ATTRIB_VALUES Click the Attributes link on

an Account or Fund Codepage to access the ChartFieldAttributes page.

Select the ChartFieldattributes to associate withthe selected ChartFieldvalue.

Miscellaneous ChartFields F2_ELEMENT_CF1 General Ledger, FederalReports, FACTS II,Miscellaneous ChartFields,Miscellaneous ChartFields

Select ChartFields to usefor recording Category BPrograms, Cohort Year,Transfer Agency, TransferAccount and TransactionPartner information.

Attribute Cross Reference F2_ATTR_XREF General Ledger, FederalReports, FACTS II, AttributeCross Reference

Enables each agency todecide on the names ofthe fund and accountattributes used in FACTS IIprocessing. Each agencycan either make up itsown names or use thenames presented in thisdocumentation.

Accounting Edits F2_ATTR_XREF_EDIT Click the Accounting Editstab on the Attributes CrossReference page.

Specify the ChartFieldAttributes and Attributevalues applicable to theAccounting Edits

Review FACTS II Data -Header Information

F2_STAGE_HDR General Ledger, FederalReports, FACTS II Review,Review FACTS II Dataand click the HeaderInformation tab if the page isnot displaying.

Enter the criteria to displaythe appropriate FACTS IIdata on the remaining pagesfor review.

Review FACTS II Data -Detail Balances

F2_STAGE_DTL1 General Ledger, FederalReports, FACTS II Review,Review FACTS II Data andclick the Detail Balances tab.

Displays the FACTS II detailaccount balances based forthe selected business unitand the criteria entered onthe Header Informationpage.

Review FACTS II Data -Detail Attributes

F2_STAGE_DTL2 General Ledger, FederalReports, FACTS II Review,Review FACTS II Data andclick the Detail Attributestab.

Displays the ChartFieldattributes associated withspecific ChartFields basedon the criteria entered on theHeader Information page.

Review FACTS II Data -Footnotes

F2_STAGE_FTNT General Ledger, FederalReports, FACTS II Review,Review FACTS II Data andclick the Footnotes tab.

Displays the FACTS IIfootnote informationassociated with the selectedbusiness unit and the criteriaspecified on the HeaderInformation page.



Page Name Object Name Navigation UsageLoad MAF Data (loadmaster account file data)

F2_RUN_MAF General Ledger, FederalReports, FACTS II Creation,Load MAF Data

Load the MAF data from afile that is sent by the U.S.Treasury to the governmentagency to review inPeopleSoft General Ledger.

Review MAF Data F2_MAF_INQUIRY General Ledger, FederalReports, FACTS II Review,Review MAF Data

Review the MAF data sentby the U.S. Treasury basedon a selected MAF TreasurySymbol.

Treasury Symbol CrossReference

F2_TSYM_XREF General Ledger, FederalReports, FACTS IIDefinition, Treasury SymbolCross Ref (reference),Treasury Symbol CrossReference

Select the Treasury Symbolattribute that correspondswith the Treasury Symbolthat is included in the MAF.

Entering FACTS II Contact InformationAccess the FACTS II - Contact Info page.

FACTS II Contact Information page

Contact ID Enter a U.S. Treasury ID number to add or modify information aboutyour agency’s FACTS II contact personnel.

First Name andLast Name Enter the first and last names of the FACTS II preparer.



Phone Number, Phone Ext,Fax Number, andEmailAddress

Enter the telephone number, phone extension, fax number, andemail address of the preparer.

Mother’s Maiden Name For security purposes, enter the maiden name of the preparer’s mother.

Supervisor Name,Supervisor’s phonenumber, andSupervisor’sPhone Ext.

Enter the name, phone number, and phone extension of thepreparer’s supervisor.

Agency Name Enter the name of the agency that is responsible for submitting FACTS II data.

Bureau Name If the FACTS II data represents a bureau or division of theagency, enter that name.

Address Line 1, AddressLine 2, City, State,Country, andPostal Code

Enter the agency’s street address (the second line is for information such asbuilding or suite number), city, state, country, and postal code.

Last Update Each time you save this record this field is updated.

Creating the Preparer FileAccess the FACTS II - Create Preparer File page.

Create Preparer File page

Contact File Enter a contact file name with a .TXT extension. Do not enter the entire path.

Reporting Year andReporting Month

Enter the year and month for this FACT II submission.

Preparer Identification Select the preparer’s identification number. You can select more than one.

Run Click this button to access the Process Scheduler Request page to run theCreate FACTS Preparer File process (GL_F2CONTACT).



Setting Up ChartField AttributesAccess the Attributes - ChartField Attribute page.

Note. You can also use Chartfield Attributes for non-FACTS II purposes.

Attributes — ChartField Attribute page

Most field values on this page are based on the ChartField Attributes table that followsthe field descriptions for this page.

Important! FACTS I and FACTS II rely on only one attribute being associated with each respective chartfield.The option to “Allow Multiple Values per Attr” should not be used with FACTS I and FACTS II attributes.

SetID Displays the setID that is set up for your FACTS II data. ChartFieldattributes are based on a setID so that they can be associatedwith more than one ChartField.

Field Name Enter the type of ChartField that each ChartField attribute applies to. Values areFUND_CODEandACCOUNTand are based on the ChartField Attribute table.

Attribute Enter a ChartField attribute from the ChartField table or define yourown attribute names for your organization. . These names and valuesare associated with the ChartField names and values required by theU.S. Treasury on the Attribute Cross Reference page.

Description Enter the description of this ChartField attribute from the ChartFieldAttributes table or create your own description.

Allow Multiple Values perAttr (allow multiple valuesper attribute)

Warning! Do not select this check box for FACTS I or FACTSII ChartField attributes.



ChartField Attribute Value Enter each attribute value from the ChartField Attributes tableor define your own values.

Description Enter the description of each attribute value from the ChartFieldAttributes table or create your own description.

ChartField Attributes Table

The ChartField Attributes table lists the ChartField attributes that you must set up for FACTS II.

In addition to the attributes listed in the following table, the Agency Location Code (ALC) is essential to theFACTS I and FACTS II processes. Donotchange the name of this attribute. Typically this attribute is associatedwith the Fund Code ChartField. The FACTS processes locate the ChartField that is associated with thisattribute to determine the ChartField that you use to record fund codes (in case you decided to use a ChartFieldother than the delivered Fund Code ChartField). Furthermore, you must associate both the ALC attribute andthe Treasury Symbol (TSYMBOL) attribute (described in the table below) with the same ChartField.

Warning! Do not change the name of the Agency Location Code (ALC) attribute.

Field Name Attribute DescriptionAllow Multiple

Values


FUND_CODE BEA BudgetEnforcement Act

N

This must always N.

D (Discretionary)

M (Mandatory)

Note. These areTreasury values.

FUND_CODE BORROW Fund borrowingsource

N

This must always beN.

P (Public)

T (Treasury)

F (FederalFinancing Bank)


FUND_CODE CATEGORY Apportionmentcategory code

N


A (Category A)

B (Category B)

C (Category C— Not subject toapportionment.)





Values


FUND_CODE EX_UNEXP Expired orunexpired authority

N


E (ExpiredAuthority)

U (UnexpiredAuthority)


FUND_CODE REIMBURSE Funding authorityindicator

N


D (Direct Authority)

R (ReimbursableAuthority)


FUND_CODE TSYMBOL Treasury Symbol N


Each agency entersits own TreasurySymbol values anddescriptions.

Example:

19X0192 (No YearRevolving Fund)19X0202 (No-YearFund)

BUDGET_REF YR_OF_BA Year of BudgetAuthority

N


BAL (Outlay frombalances broughtforward fromprevious year.)

NEW (Outlaysfrom New BudgetAuthority)

ACCOUNT ADVANCE FLG Advance Flag N


F (Advance inFuture Year)

P (Advance in PriorYear)

X (Not Applicable)




Values


ACCOUNT AUTHORITY Authority type N


B (BorrowingAuthority)

C (ContractAuthority)

P (Appropriation)

S (Spendingfrom OffsettingCollections)

D (AdvanceAppropriation)

L (Proceeds of LoanAsset Sales withRecourse)

ACCOUNT AVAIL_TIME Budget resourceavailability

N


A (Available in thecurrent period.)

S (Available in thesubsequent period.)

ACCOUNT BEGIN_END Begin or endbalance code

N


B (ReportBeginning Balanceto Treasury)

E (Report EndingBalance toTreasury)

Y (Report bothBeginning andEnding Balancesto Treasury.)

ACCOUNT DEB_CRED Debit/Creditindicator

N


CR (Normal CreditBalance)

DR (Normal DebitBalance

ACCOUNT DEF_INDEF Definite/Indefiniteflag

N


D (Definite)

I (Indefinite)




Values


ACCOUNT FACTSII FACTS II SGLaccount indicator

N


Y (FACTS IIAccount)

ACCOUNT FUNCTION OMB FunctionCode

N


DEF (Defense)

NND (Non-Defense)

ACCOUNT IGN_ON_EXP Ignore onexpiration.

N


Y (Yes, ignore onexpiration)

N (No, do not ignoreon expiration.)

ACCOUNT RT7 Record type 7

This attributeindicates the RT7value for a specificaccount. Thisedit is used in theprocessing logic forthe PreEdit and Edit6 in the FACTS IIValidation process.

Y

This is one placewhere you shoulduse Y.

911 (Discount onInvestments)

921 (Imprest Fund)

941 (ContractAuthority)

951 (Authorityto Borrow fromTreasury)

961 (ExchangeStabilization Fund)

962 (Authority toBorrow from thePublic)

971 (Investmentsin Public DebtSecurities)

972 (Investments inAgency Securities)




Values


ACCOUNT ED00 Pre-edit

Pre-edit identifiesthe valid RT7values for a specificaccount. Someaccounts mayhave multiple RT7values.

N


911 (Discount onInvestments)

921 (Imprest Fund

941 (ContractAuthority)

951 (Authorityto Borrow fromTreasury)

961 (ExchangeStabilization Fund)

962 (Authority toBorrow from thePublic)

971 (Investmentsin Public DebtSecurities)

972 (Investments inAgency Securities)

ACCCOUNT EDIT1 Edit 1

Validates that theending DR balancesof budgetaryaccounts withina fund equals theending CR balanceof budgetaryaccounts within afund.

N


EXCLUDE(Exclude formAccounting Edit1 DR-CR Valuation)




Values


ACCOUNT EDIT2 Status of Funds andTotal ResourcesBalances.

This edit simulatesthe calculation ofLines 7 and 11 fromSF133 .

N


ST_BEGIN (Statusof Funds, BeginningBalance)

ST_CURRENT(Status of Funds,Current Indicator)

ST_ENDING(Status of Funds,Ending Balance)

ST_CR_TO_CR(4060, 4070, 4210,and 4310, ST or TOIndicator)

TO_BEGIN(Total Resources,Beginning Balance)

TO_CURRENT(Total Resources,Current Balance)

TO_ENDING (TotalResources, EndingBalance)

ACCOUNT EDIT3 ResourcesChartField lessObligationChartField

ResourcesChartField lessObligationChartField. Thisedit validates thatthe beginningbalance budgetarydebits equal thebeginning balancecredits.

N


S1 (ResourcesCarried Forwardless ObligationsCarried Forward)

S2 (EqualUnobligated StatusCarried Forward)




Values


ACCOUNT EDIT4 Zero balanceby Quarter 4 foraccounts

Zero Balanceby Quarter 4for AccountsBudgetaryaccounts relatedto anticipated itemsare not allowed tohave balances atthe end of the 4thquarter. This editchecks that each ofthe accounts withan EDIT4 accountattribute have abalance which isequal to zero.

N


ZEROBYQ4 (ZeroBalance by theFourth Quarterfor AnticipatedAccounts)

ACCOUNT EDIT5 Fund Equity andFund ResourcesBalances

This edit checksthat the sum of thefund resourcesaccounts mustequal the sum of theequity accounts froeach appropriationsymbol.

N


FE_END (FundEquity, EndingBalance)

FR_BEGIN(Fund Resources,Beginning Balance)

FR_END (FundResources, EndingBalance)

FR_END_BC (FundResources, EndingBalance, AuthorityB or C)

ACCOUNT EDIT6 Beginning andEnding Balances

This edit will findthe sum of either thebeginning or endingbalance for eachaccount that has alike RT7 value andcompare it to thepre-closing balancefrom the TreasuryMAF.

N


BEGIN (BeginningBalance)

END (EndingBalance)




Values


ACCOUNT EDIT7 Edit fund balancewith Treasurycalculation.

This edit comparesthe ending balanceof accounts 1010,4350, and 4391for each non-RT7appropriationsymbol to thepre-closing balanceon the MAF file.

N


FBWT_CALC(Fund Balance with.Treasury)

ACCOUNT EDIT10 Cancellation Edit

This edit isused for allcancelling TreasuryApproppriation/Fund Symbols(TAFS). It checksfor zero balancesin reimbursableorders, receivables,obligations,payables, andunobligatedbalances.

N


GROUP1 (Group1 [2108 Column 7]must be 0)

GROUP2 (Group2 [2108 Column 9]must be 0)

GROUP3 (Group 3[2108 Column 10]must be 0)

GROUP4 (Group 4[2108 Column 11]must be 0.)




Values


ACCOUNT EDIT11 This edit validatesthat the sum ofcertain accountshave a normal Debitor Credit balance.

N


GROUP1 (Group1 [2108 Column7] Normal DRBalance)

GROUP2 (Group2 [2108 Column9] Normal DRBalance)

GROUP3 (Group3 [2108 Column10] Normal CRBalance)

GROUP4 (Group 4[2108 Column 11]Normal CR Balance)

GROUP5 (Footnoteis always required.)

ACCOUNT EDIT12 Collections andDisbursementsAccounts ( OutlayEdit)

This edit comparesthe sum of theEDIT12 accountsfor the from andto period specifiedon the AccumulateFACTS II Data runcontrol panel, to theTreasury suppliedOutlay Amount.

N


COLLECTIONS(CollectionsAccount)

DISBURSEMENTS(DisbursementsAccount)

Linking Attributes ChartFieldsAccess a ChartField such as Account or Fund Code or Budget Reference that requires attributes.



ChartField Values - Account page

Attributes Click this link to associate the ChartField attributes that you set up forFACTS II with the appropriate Account value(or Fund Code ChartFieldvalue on the Fund Code page or Budget Reference ChartField value onthe Budget Reference page) required for FACTS II reporting.

Selecting ChartField AttributesAccess the ChartField Attribute page.

ChartField Attribute page

ACCOUNT After selecting the Attributes link for an Account ChartField (Fund Code), arow that contains values for SetID, ChartField Value, Effective Date and theField NameACCOUNT (FUND_CODE, BUDGET_REF)displays.

ChartField Attribute Select the appropriateChartField Attribute for this ChartField Value.

ChartField Attribute Value Select the ChartField Attribute Value for this ChartField attribute. You canadd as many rows of ChartField Attributes and ChartField Attribute Valuesfor the selected ChartField Value (in this example, Account 4042).



See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining and Using ChartFields,” Adding Fund Code Values

Linking Account Attributes and Values to Account ChartFieldsAccess the appropriate Account page.

Specifying Miscellaneous ChartFieldsAccess the Misc Fields page.

Miscellaneous ChartFields page

Note. You can change the delivered ChartField specifications to any configurable ChartField. For example,the FACTS II Data Element FED_NONFED is associated with Transaction Partner. You can change this to anyother configurable ChartField. However, you must use different ChartFields for each of the FACTS II DataElements. The exceptions to this rule are the ChartFields for Transfer Account and Transfer Agency. Theymay use the same configurable ChartField or two different ChartFields. In this example, Trading Partner isassociated with both of these FACTS II Data Elements. Your decision to use either a single ChartField forTransfer Agency and Transfer Account, or separate ChartFields, obviously has an effect on how you will enterdata into your ledger. Some of these CharField names are the result of a ChartField configuration.

Description PeopleSoft predefines theCategory B program, Cohort year ,Federalor Non Federal Partner, Transfer Account and Transfer Agencydata elements and descriptions.

ChartField Name Select a configurable ChartField for each FACTS II Data Element. SinceTransfer AgencyTransfer Accountare related, you can assign the sameconfigurable ChartField to them, if desired, or set them up with separateconfigurable ChartFields. All other FACTS II Data Elements must beassociated with different configurable ChartFields.



See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining and Using ChartFields,” Adding Fund Code Values

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, Enterprise Service Automation,and Supply Chain Management PeopleBook, “Defining and Using ChartFields,” Adding Account Values

Setting Up Attribute Cross-ReferencesAccess the FACTS II - Attribute Xref page.

Note. . Existing customers who are implementing this enhancement should re-open theAttribute Xref and Accounting Edits pages and enter the ChartField Attribute names for thenew data elements introduced by this enhancement.

Attribute Cross Reference page

Description These are the predefined attributes that the FACTS II processesrequire by the U.S. Treasury requirements.

ChartField PeopleSoft predefines theField Name forACCOUNTandFUND_CODE.

ChartField Attribute andChartField Attribute Value

Select the ChartField attributes and attributes values that you definedas cross-references to each Data Element.

Note. The values selected are only examples.

Selecting Attribute Cross References for FACTSII Accounting EditsAccess the Accounting Edits page.



Accounting Edits page

ChartField Attribute andChartField Attribute Value

Select the attributes and attribute values that you defined to cross-referenceeach of the predefined data elements listed on this page.

Note. Refer to Review FACT II Data, Detail Attributes to review attributes for eachChartField value for a selected business unit and period.

Loading MAF DataAccess the Load MAF Data page.

Load MAF Data page

Click the Add Attachment button and type the path and file name, or click theBrowse button to navigate to your MAF file location. Click the Upload buttonto store the file as an attachment. The file appears in the Attached File field.

At the beginning of each fiscal year, the U.S. Treasury sends a MAFcontaining the U.S. Treasury account fund symbols (TAFS) for a specificagency long with the preparer and certifier IDs for each symbol.



Along with this data, the U.S. Treasury sends a spreadsheet containingthe attributes for each SGL account. You can use this spreadsheet tovalidate that your data is set up correctly.

Run Click this button to upload the file using the PS/GL MAF Load(F2_MAF_LOAD) process. This loads the file’s data to theappropriate database table.

Note. The Add, Delete, and View Attachment buttons work the same way as they do for FACTS I.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Loading MAF and FACTS I Data, page 523.

Reviewing the MAF FileAccess the Review MAF Data page.

Review MAF Data page

MAF T.Symbol (masteraccounting file treasurysymbol)

Stores the Treasury Symbol in the format that is defined by the U.S. Treasuryfor FACTS II processing. This Treasury Symbol is different from the TreasurySymbol format that is required by most other Treasury reporting.

MAF Seq Num (masteraccounting file sequencenumber)

The U.S. Treasury supplies this number. If the Treasury sends the agencya new MAF file, this number is incremented.

Record Type 7 TAS(recordtype 7 treasury appropriationfund symbol)

The application displays a 3-digit numeric code that is attached to the endof the Treasury Appropriation Fund Symbol. This code identifies the typeof fund resources, such as Fund Held Outside of the Treasury, Authorityto Borrow from the Treasury, and Unrealized Discounts.

Dept Reg(departmentregular)

Displays a regular (versus a transfer) department number that isassociated with this MAF Treasury Symbol.



Dept Trans (departmenttransfer)

Displays a transfer (versus a regular) department number that isassociated with this MAF Treasury Symbol.

Fiscal Year TAS fiscalyear treasury appropriationfund symbol

Displays the funding period of the appropriation that applies tothis MAF Treasury Symbol.

Main Acct main account Displays the main account used for this MAF Treasury Symbol.

Sub Acct sub account Displays a Sub Accountused for this MAF Treasury Symbol.

Acct Split Seqaccountsplit sequence

Displays the account split that is provided by the Office of Management andBudget interface file. Any number that is greater than 000 is an account split.

Preclosing Balance Displays this department’s remaining appropriation balance priorto the close of the fiscal year.

Net Outlays Displays the net collections and disbursements reported to date by thisdepartment for the current fiscal year to the U.S. Treasury.

Master Preparer Ind(master preparer indicator)

Identifies whether a master preparer is required. This is only necessaryif an account split applies to this account.

Acct Split Alloc Ind(account split allocationindicator)

Indicates if the master preparer divided the account balance amongthe members of an account split.

Preparer Identification Displays the FACTS II preparer’s name for this department.

Chapter Displays the Chapter number that is used in the Treasury’s Annual Report.

GOALS Flag (governmentonline accounting link flag)

Indicates that the FACTS II file can be imported to the GovernmentOn-line Accounting Link System (GOALS).

Appropriation Flag Indicates that an appropriation is associated with this MAF Treasury Symbol.

Certify Flag Indicates whether this MAF Treasury Symbol is required by the BudgetReports Branch of the Financial Management Service.

Borrow Flag Indicates whether a borrowing source is required for thisMAF Treasury Symbol.

Bulk/Non-Bulk Flag Y indicates that you want to send the FACTS II information in abulk transfer file. N indicates that you want to send the FACTS IIinformation in a non-bulk transfer file.

FMS Source Indicator(financial managementservices source indicator)

The FMS interface indicator.

OMB Source Indicator(office of management andbudget source indicator)

The OMB interface indicator.



Setting Up the FACTS II Treasury Symbol Cross-ReferencesAccess the Treasury Symbol Cross Reference page.

Treasury Symbol Cross Reference page

SetID Select theSetID that applies to the FACTS II reporting data.

Treasury Symbol Attribute Select the attribute that corresponds to the MAF Treasury Symbol.

MAF Treasury Symbol(master accounting filetreasury symbol)

Select the MAF Treasury Symbol, which is imported from theU.S. Treasury MAF file.

Cancelling Year Select this option if the Treasury Symbol is beyond the Cancelling Year.FACTS II determines the Cancelling Year by adding six years to the last yearof availability. You must select this option to enable Edit 10 to process.

After Expiration Year Select this option if this Treasury Symbol expired. If a Treasury Symbolexpires, zero-balanced rows cannot be reported to the FACTS II Importfile. To identify the accounts associated with an expired Treasury Symbol,you must select the Ignore on Expiration (IGN_ON_EXP) attribute andselect Y for the attribute value on the Attribute Xref page.

Creating FACTS II TreesTo set up FACTS I trees, use the following components:

• Tree Manager (PSTREEMGR)

• FACTS Tree Group (FACTS_TREE_GRP)

• TableSet Control (SET_CNTRL_TABLE1)


• Use trees to control the roll-up of ChartField data.

• Create the FACTS II Account Rollup tree.

• Create the FACTS II Cohort Year tree.

• Create the FACTS II Category B tree.



• Create the Accts Requiring Attributes tree.

• Create the Transfer Agency tree.

• Create the Transfer Account tree.

• Create the Transaction Partner tree.

• Create a Tree Group for FACTS II.

• Configure TableSet Control for FACTS II Processing.

• Configure the TableSet Control Record Group Page.

• Configure the TableSet Control Tree Page.

Pages Used to Create FACTS II Trees


Tree Definition andProperties

PSTREEDEFN Tree Manager, CreateTree, Tree Definition andProperties

Create a new tree to identifythe tree name, relatedstructure ID, setID, and anyother rules or characteristicsof the tree.

Tree Manager PSTREEMGR Tree Manager, Find anExisting Tree

Access an existing tree withoptions that enable you toaccess and modify the treedefinition and properties,print, and configure treedisplay options.

FACTS Tree Group FACTS_TREE_GRP General Ledger, FederalReports, FACTS Tree Group

Contains all of the FACTS IItrees and the roll-up level.This page is identified onmost of the run control pagesfor FACTS II reporting andprocessing.

TableSet Control - RecordGroup

SET_CNTRL_TABLE1 PeopleTools, Utilities,Administration, TableSetControl, Record Group

Defines all the recordgroups based on a specificSet Control Value and theirassociated setIDs. Alsoidentifies the default setIDof the General Ledgerbusiness unit.

TableSet Control - Tree SET_CNTRL_TABLE2 Tools, Administration,TableSet Control, Tree

Set up tree values on thistable if your setID for yourbusiness units do not matchyour default setID.

See Also

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Using Trees to Summarize ChartFields

PeopleTools PeopleBooks: PeopleSoft Tree Manager



Using Trees to Control Roll-up of ChartField DataIt is possible that your Account, Fund Code, or other ChartField values may not match those specifiedby U.S. Treasury for reporting purposes. To accommodate these mandates, you must create trees thatcontain nodes representing the Account or other ChartField values required by the Treasury for FACTSreporting. Under these nodes, you specify the actual detail values used in your ledgers, which roll upinto the U.S. Treasury values for reporting. The FACTS II process finds the tree node names whenit accumulates reporting data and uses these names when it creates the reporting files. In general, it isvery important that the tree node names follow the US Treasury file’s field specifications.

You use the PeopleSoft Tree Manager to create all trees. You can use the tree names, levelnames, and structure IDs that appear in the following examples, or you can create your own.You can copy an existing tree structure or create a new one.

FACTS II Account Rollup Tree Definition

This is a typical example of a FACTS II tree definition.

See Also




Creating a FACTS II Account Roll-up TreeCreate a FACTS II Account Roll-up tree in PeopleSoft Tree Manager similar to this example. Before youcreate this tree, you must define your Account ChartField values and determine your detail structure.

FACTS II Account Rollup Tree

The FACTS II Account Rollup Tree stores the hierarchical relationship between SGL accounts that youreport to the U.S. Treasury for FACTS II and an agency’s posting accounts. The FACTS II Accumulationprocess uses this tree to roll up the posting level account ChartField values into the SGL accounts. Eachagency may have a different combination of lower level posting accounts that roll up to a SGL accountstructure that is mandated by the U.S. Treasury for FACTS II reporting. Determine the lowest level ofdetail that you need for your Account ChartField structure to capture all possible combinations of USSGLaccounts and FACTS II attributes, as well as additional agency-specific posting detail.

Your agency can use any tree and level names as long as you specify these names on the FACTS II Tree Group.You must create the FACTS II Account Rollup Tree in order to run the Accumulate FACTS II Data process.



Creating a Cohort Year TreeCreate a Cohort Year tree similar to this example.

FACTS II Cohort Year Tree

Create a Cohort Year Tree at the COHORTYEAR tree level for each cohort year basedon your agency’s reporting needs. Enter the appropriate detail values that identify whichChartField values (loans) roll up to a particular cohort year.

The Cohort Year Tree is the exception to the rule that the FACTS II tree node names should alwaysmatch the values required by US Treasury. In this instance, Cohort Year values in the FACTS II fileare only 2 positions. However, the tree is set up with 4 character node names to keep it consistent withthe Cohort Year tree in earlier releases, as well as with the way the program derives the Cohort Yearvalues. The program will take the third and fourth character of the node name to derive the FACTSII file Cohort Year values, for example, 1975 becomes 75 in the FACTS II file.

The Accumulate FACTS II Data process uses this tree to identify ChartField values that represent loansassociated with a cohort year for the production of the FACTS II Treasury input file. In this example,the loan numbers roll up to the COHORTYEAR tree level, which contains the cohort year informationrequired for FACTS II reporting. You may also use a different configurable ChartField for this purpose.Since an agency may have projects that are not loans and are not associated with a cohort year, thistree is used to distinguish between the two types of project ChartField values. Each agency shoulddetermine the ChartField structure that it needs to satisfy its cohort year requirements.

Note. You must set up the ChartField values prior to creating this tree.

Creating a Category B TreeCreate a Category B tree in PeopleSoft Tree Manager based on this example.



FACTS Category B Tree

The Accumulate FACTS II Data process uses this tree to identify category B programs and to extract the3-digit program sequence number and category B program description needed for the production of theFACTS II Treasury Input file. Your agency may have programs that are both category B and non-categoryB programs. This tree is useful to distinguish between these two types of programs. Each agency shoulddetermine the ChartField structure that satisfies its category B and non-category B reporting requirements.The tree level specified on the FACTS Tree Group page identifies the node values and node descriptionsthat contain the three digit sequence number and category B program description respectively.

You may use any tree name and level name as long as you specify the desired tree name and level name on theAccumulate FACTS II Data page. This tree is required for the Accumulate FACTS II Data process (GLS8302).

Note. You must set up Program ChartField values prior to creating the Category B Tree.

Creating the Accounts Requiring Fund Attributes TreeCreate an Accounts Requiring Fund Attributes tree using PeopleSoft Tree Manager based on this example.



FACTS II Account Requiring Fund Attributes Tree

The FACTS II Accounts Requiring Attributes tree stores the relationship between theChartField attributes required for FACTS II processing and their associated SGL accounts.This tree replaces the F2_FND_ATTR_ACCTS tree.

The purpose of this tree is to filter out the attributes for accounts that do not require certain attributes tobe reported. After the FACTS II Accumulation process accumulates all the attribute data, it checks theaccumulated attributes against this tree to see if they are required to be reported. If the attribute is not required,it is removed from the staging table and is not included in the FACTS II file. To determine the attributesto be reported for any given account, the program takes the account from the ledger (such as 4119) andsearches for the account in the FACTSII_ATTRIBUTES tree. The account may appear under numerousnodes depending on which attributes are required for that specific account. Wherever the program findsthe account in the tree, the attribute is considered as required for reporting. If the program has previouslyaccumulated an attribute value for the account, but is unable to locate the account under that respectiveattribute’s node, the accumulated attribute value will be excluded from the FACTS II file.

The F2_REQ_ATTR_ACCTS Tree and ACCOUNT Level are examples of values that the FACTS IIprocesses can use. You can create your own tree name and level name, as long as you specify the treename and level name on the FACTS Tree Group page. You must set up this tree to run the AccumulateFACTS II Data process (GLS8302) and the GL Activity with Attributes Rpt (GLS7017).

Make sure that this tree consists of all accounts required by the U.S. Treasury for each attribute.If your agency does not use an account that the U.S. Treasury requires, then the agency doesnot have to define the account on this tree. The fund code and account ChartField attributesare predefined and delivered in the PeopleSoft sample data.



There are four node names that must be named exactly as specified:

• PUBLIC_LAW

• FED_NONFED

• TRF_AGENCY

• TRF_ACCT

All other nodes must be named exactly the same as the attributes listed on the AttributeXref page. For example, if the user has called their Authority Type attribute AUTH insteadof AUTHORITY, then the node name must be AUTH.

These attribute nodes are not required on the Accounts requiring Attributes tree:

• The Normal Balance, Debit and Credit, and Begin End because these attributes are always required toprocess FACTS II. The program does not check against this tree for these attributes.

• The TAFS status attribute because it is not required in the FACTS II flat file.

• The Transfer To/From and Deficiency Flag because these values will be derived by the U.S. Treasury.

Note. The U.S. Treasury’s SGL Account Attributes Required for FACTS II Reporting of Detailed FinancialInformation defines these rules. This information is available at the U.S. Treasury Department’s website.

Creating the Transfer Agency TreeCreate the Transfer Agency tree using PeopleSoft Tree Manager based on this example.



FACTS Transfer Agency Tree

This tree contains nodes for each of the transfer agencies. If you have decided to use the same ChartField forboth Transfer Agency and Transfer Account, then the values in your ledger for that ChartField will representboth Transfer Agency and Transfer Account at the same time. The tree will allow the program to translate theledger’s combination Transfer Agency/Account value to the Transfer Agency value required by US Treasury.

Creating the Transfer Account TreeAccess Tree Manager to create the FACTS II Transfer Account Tree:



FACTS II Transfer Account Tree

This tree contains nodes for all the US Treasury transfer accounts. The leaves are made up of ChartField valuesfrom your ledger representing Transfer Accounts. If you decide to use the same ChartField for both TransferAgency and Transfer Account, then the values in your ledger for that ChartField will represent both TransferAgency and Transfer Account at the same time. The tree will allow the program to translate the ledger’scombination Transfer Agency/Account value to the Transfer Account value required by US Treasury.

Creating the Transaction Partner TreeAccess Tree Manager to create the FACTS Transaction Partner tree.



FACTS Transaction Partner Tree

The three nodes on this tree represent the three types of Transaction Partners: Non-Federal, Federal,and Non-Federal Exception. The leaves represent all the detail transaction partner ledger data thatroll up into each type of Transaction Partner for FACTS II processing.

Prior to this release update, you had to set up variations of account numbers to indicate whether theaccount used in any particular transaction pertains to another Federal organization. You did this by addingsuffixes to account numbers. For example, the suffix ‘G’ was added to account ‘1610’ to create account‘1610G’. Also, the XPARTNER attribute was also only capable of indicating one attribute value at atime. Now, PeopleSoft enables you to use one of the configurable ChartFields to record the TransactionPartner attribute. This means that the Transaction Partner attribute is independent from the AccountChartField, which eliminates the need to create and use variations of the same account.

If you are an existing customer, you can use the new separate ChartField approach or you can continue touse the multiple account approach. If you are part of the way into a year, you must use the multiple accountapproach until you get to the end of the year since all of your existing year-to-date data uses this method.

Using this older method, your Transaction Partner tree is designed differently andshould be based on the following example.

Node ALL – All Transaction Partners

• Node E – NonFederal Exception

- 1010 E

- 1020E

• · Node F – Federal

- 1010G

- 1020G

• · Node X – Non Federal



- 1010X

- 1020X

Creating a Tree Group for FACTS IIAccess the FACTS Tree Group page.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Creating a Tree Group for FACTS I, page 518.

FACTS II Trees andTree Levels

The FACTS Tree Group page lists all of the tree names required for FACTS IIprocessing. Select the name of your FACTS II tree that represents the listedTree Name. Select the tree level used for summarizing your FACTS II data.

Configuring TableSet Control for FACTS II ProcessingYou should carefully choose the setIDs used for the FACTS Tree Group and the FACTS II Trees and configurethe TableSet Control setIDs accordingly. Incorrect configuration could result in the unavailability of tree groupnames or tree names in prompt lists on pages, or in the inability of the FACTS II process to retrieve data.

If you have only one business unit in your organization and use only one setID to set up your ChartFields, trees,and tree groups, then your TablesSet Control setIDs should all be the same and do not need changing. Also, ifyou use more than one business unit that uses the same default setID, then the Control Tables should not needto be modified. However, check the TableSet Control pages for each business unit and setID, using their valuesas the Set Control Values, to ensure that all tables and trees are using the same setID. Note that the Tree Grouptable is in the new GL_15 Federal Reports Record Group in the TableSet Control Record Group page.

If you use more than one SetID in your organization for setting up your ChartFields, trees, and tree groups,then you must make sure each setID that you use is set up correctly in TableSet Controls. The setIDs usedin the following steps are only examples, your organization may use something different.

1. Set up your FACTS II ChartFields, trees, and tree group using the FEDRL SetID.

2. Identify the general ledger business unit (for example, FED01) that you want to use for FACTS IIprocessing. Access the SetControl Value (FED01) in TableSet Control. The Default SetID on the TableSetControl Record Group page is the default setID that you set up for the general ledger business unit.

3. Find the GL_15 Federal Reports Record Group and select the setID (FEDRL) for GL_15 tomatch the setID (FEDRL) that you used to create your tree group.

The FACTS Tree Group table is a part of the GL_15 Record Group and must have the samesetID. This step enables the Tree Group dropdown list to appear on the Accumulate FACTS IIData page so that you can select a FACTS Tree Group to process.

4. Is the Default SetID (SHARE) on the TableSet Control Record Group page the same as thesetID that you used to set up your trees? YES or NO?

The FACTS II processes normally refer to the Default SetID in the TableSet Control RecordGroup page and uses the default setIDs to retrieve the FACTS II tree.

5. If YES, you can save and exit TableSet Control.

6. If NO, you must enter each tree on the TableSet Control – Tree page that has a setID that is differentfrom the Default SetID on the TableSet Control – Record Group page.



7. If you run FACTS II processing on multiple business unit, repeat these steps.

Configuring the TableSet Control Record Group PageAccess the Record Group page.

TableSet Control - Record Group page

Set Control Value To run the FACTS II Accumulation and Validation processes, you mustenter a business unit. The business unit you use is theSet ControlValue that you select to ensure that the FACTS II tree group and treesare accessible during FACTS II processing.

Default SetID This is the Default SetID for the general ledger business unit that you enteredas your Set Control Value and that you intend to use for processing FACTS II.

Record Group ID andDescription

Find the Record Group ID,GL_15 Federal Reports. This recordgroup contains the FACTS Tree Group table.

SetID Select a SetID for this record group that matches the setID that youused to set up the FACTS Tree Group to use in the AccumulateFACTS II Data process (GLS8302.)

The selected SetID enables you to display a list of FACTS Tree Groupsand select the Tree Group name in the Accumulate FACTS Data pagethat you want the FACTS II GLS8302 process to access.



Note. You do not need to change anything on either of the TableSetControl pages if you use only one SetID as the default for the businessunit that you intend to use for FACTS II processing and for setting upyour FACTS II ChartFields, trees and tree group.

Configuring the TableSet Control Tree PageAccess the TableSet Control -Tree page.

TableSet Control - Tree page

Tree Name Add any FACTS II trees that are set up using a setID that is differentfrom the Default SetID on the Record Group page.

Generating a FACTS II Flat FileThis section discusses how to:

• Review the FACTS II data setup.

• Accumulate the FACTS II data.

• Review the FACTS II validated data.



• Validate the FACTS II data.

• Create FACTS II file.

Note. Make sure you have completed all the preceding FACTS II tasks before you start the tasks in this section.

Pages Used to Generate a FACTS II Flat File


ChartField Attribute Inquiry ATTR_INQ Setup Financials/SupplyChain, Common Definitions,Design ChartFields,Review, Review ChartFieldAttributes

Enables you to review theattributes for FACTS IIprocessing prior to runningthe FACTS II Accumulation(GLS8302) process.

Accum FACTS II Data(accumulate FACTS II data)

F2_RUN_GLS8302 General Ledger, FederalReports, FACTS II,Accumulate FACTS II Data

Accumulate FACTS II dataand load it into stagingtables.

F2 Staging Header F2_STAGE_HDR General Ledger, FederalReports, FACTS II, ReviewFACTS II Data, F2 StagingHeader

Select data to set up theStaging Header information;enter the net period outlaythat is to apply to the FACTSII file.

Detail - Balances F2_STAGE_DTL1 General Ledger, FederalReports, FACTS II,Review FACTS II Data,Detail-Balances

Review all of your FACTS IIACCOUNT and FUNDCODE detail balances,including other ChartFielddetails that apply.

Detail- Attributes F2_STAGE_DTL2 General Ledger, FederalReports, FACTS II, ReviewFACTS II Data, Detail-Attributes

Review the assignedattributes and attributevalues for each FACTSII ACCOUNT andFUND_CODE .

Footnotes F2_STAGE_FTNT General Ledger, FederalReports, FACTS II, ReviewFACTS II Data, Footnotes

Enter footnotes for eachFACTS II account and fundcode where applicable.

Validate FACTS II data F2_RUN_GLS8303 General Ledger, FederalReports, FACTS II

Validate the accumulateddata and creates a reportthat indicates whetherthe Accounting Editprocesses passed or failedand describes the reason thatthe edit passed or failed.

Create FACTS II File F2_CREATE_FILE General Ledger, FederalReports, FACTS II

Create the FACTS II flat fileto send to the U.S. Treasuryto upload to GOALS.



Page Name Object Name Navigation UsageLedger with Attributes RUN_GLS7017 General Ledger, Federal

Reports, FACTS II, Ledgerwith Attributes

Generate a FACTS II reportfor a specific business unit,ledger, fiscal year, periodrange, adjustment periodinformation, and FACTS IICohort and Acct Req Fundattributes tree-level data.You can also indicate thatthe numeric field can be23 integers and 3 decimalplaces.

Reviewing FACTS II Data SetupAccess the Review ChartField Attribute page.

Review ChartField Attributes



SetID, ChartField,Attribute, Attribute Value,and As-of-Date

Select the appropriate criteria for a query that enables you toverify that your attributes are set up correctly before you run theAccumulate (GLS8302) process.

Accumulating the FACTS II DataAccess the Accumulate FACTS II data page.

Accum FACTS II data page

Unit Select the business unit for this FACTS II data.

Report ID Enter the FACTS II Report Identification for your agency.

Reporting Year andReporting Month

Enter the reporting year and month for this FACTS II file.

Fiscal Year Enter the fiscal year for this FACTS II data.

FACTS Tree Group Select the FACTS Tree Group for FACTS II processing.

From Period andTo Period Enter the accounting periods for this accumulated data for thepreviously entered fiscal year.


Select this check box to include closing adjustments in your FACTS II data.

Adjustment Periods Select the adjustment periods that you want to include in the accumulationof this FACTS II data. You have one or more rows.

Treasury Symbol Attribute Select the Treasury Symbol attribute that is associated with the fundsthat you are using in your FACTS II data.



Preparer identification andCertifier Identification

Select the ID of the preparer of the data for this Treasury Symbol attributeand the ID of the person who certified this preparer’s FACTS II data.

Reviewing the FACTS II Header InformationAccess the Review FACTS II Data - Header Information page.

Review FACTS II Data - F2 Staging Header page

Reviewing the FACTS II Detail BalancesAccess the Detail - Balances page.



Review FACTS II Data - Detail Balances page

This page contains all of the detail information for a specific fund code and its associatedPeopleSoft General Ledger and FACTS II accounts.

Reviewing the FACTS II Detail AttributesAccess the Detail- Attributes page.



Review FACTS II Data - Detail Attributes page

You can review the attribute values assigned to each FACTS II fund code and account.

Reviewing and Modifying FACTS II FootnotesAccess the Footnotes page.

Review FACTS II Data - Footnotes page

Enter any necessary footnotes based on your organization’s data.

Note. Review this information thoroughly before continuing with your FACTS II processing.



Validating the FACTS II DataAccess the Validate FACTS II Data page.

Validating FACTS II data page

Business Unit Business unit for this FACTS II reporting.

Report ID Enter the Report ID that you entered to accumulate the FACTS II data.

Display Full Numeric Field If you report amounts larger than 15 integers and 2 decimal places,select this option to display full numeric fields consisting of 23 integersand 3 decimal places on the Validation report.

The validation process performs edits against the account balancesgenerated by the accumulation process. It compares the current period netoutlay amount entered to the amount extracted in edit 12 and generatesa report that indicates a Pass or Fail for each edit.

Creating the FACTS II FileAccess the Create FACTS II File page.



Create FACTS II File page

Report ID Enter the accumulated and validated FACTS II report ID.

Business Unit Select the business unit for this FACTS II data.

SGL Acct File (SGLaccount file)

Enter the name of the FACTS II flat file. You must use a .TXTfile extension. Do not enter a path.

Treasury Symbol Attribute Select one or more Treasury Symbol attributes for this FACTS II data.

Running the Ledger With Attributes ReportAccess the Ledger with Attributes Report page.

Ledger with Attributes Report page



Run Click this button to generate the Ledger Activity report (GLS7017)containing the specified business unit ledger’s fund and account attributesfor the specified fiscal year and period range. This report can includejournal detail and draws its data from the Cohort Year tree and leveland the Accts Req Fund attributes tree and level.

Display Full Numeric Field Select if you report amounts larger than 15 integers and 2 decimalplaces. This displays full numeric fields consisting of 23 integersand 3 decimal places on this report.

Creating SF224, SF1219, and SF1220 ReportsTo create SF224, SF1219, and SF1220 reports, use the SF1219 Report Definition component (SF1219_DEFN)and the SF224/ SF1220 Report Defn component (SF224_SF1220_DEFN).


• Define the SF224/SF1220 accounts.

• Define the SF224/SF1220 entry events.

• Generate the SF224/SF1220 report data.

• Print the SF224 report and create a flat file.

• Define the SF1219 report.

• Print the SF1219 report.

• Print the SF1220 report.

• Create the SF1219/1220 flat file.

Understanding SF224/1220 and SF1219 ReportingPeopleSoft enables you to define and generate these balance reports in either an electronic orprinted format based on transactions that include associated entry events that flow from PeopleSoftPayables, Purchasing, and Receivables into General Ledger.

• SF224 Statement of Cash Transactions report can be printed or submitted electronically to the US Treasury.

• SF1220 Statement of Transactions According to Appropriations, Funds, and Receipt Accounts reportcan be printed separately, or combined with the SF1219 report and submitted electronically.

• SF1219 Statement of Accountability report can be printed separately, or combined withthe SF1220 report and submitted electronically.



Pages Used to Define and Generate the SF224/1220 and SF1219 Reports


Accounts SF224_SF1220_DEFN1 General Ledger, FederalReports, SF224/1219/1220,SF224/1220 ReportDefinition, Accounts

Add the range of accountsto access and use for thisreport.

Entry Events SF224_SF1220_DEFN2 General Ledger, FederalReports, SF224/1219/1220,SF224/1220 ReportsDefinition, Entry Events

Add the source transactions,entry events, and indicatewhether this transaction is acollection or disbursementfor this report.

Undeposited Accounts SF224_UNDEP_ACC General Ledger, FederalReports, SF224/1219/1220,SF224/1220 ReportsDefinition, UndepositedAccounts

Identifies a range ofundeposited accounts to useon the reports.

Generate SF224/SF1220 RUN_SF224_SF1220 General Ledger, FederalReports, SF224/1219/1220,Generate SF224/1220 Data

Runs the GLSF224G SQRprocess to update the stagingtables.

Run SF224/Flat File RUN_SF224_SF1220 General Ledger, FederalReports, SF224/1219/1220,Run SF224 Report/CreateFile, Run SF224/Flat File

Runs GLSF224/1229P SQRto print the report. Also runsGL_224_1220 ApplicationEngine create a SF224flat file.

SF1219 Definition SF1219_DEFN General Ledger, FederalReports, SF224/ SF1219/SF1220, SF1219 ReportDefinition, SF1219Definition

Set up report lines for eachaccount, its associated entryevent source transaction, andassociated entry event.

Print SF1219 Report RUN_SF1219 General Ledger,Federal Reports,SF224/SF1219/SF1220,Run SF1219 Report, PrintSF1219 Report

Runs the GLSF1219 SQRReport process to printthe SF1219 Statement ofAccountability report.

Print SF1220 Report RUN_SF224_SF1220 General Ledger, FederalReports, SF224/ SF1219/SF1220, Run SF1220Report, Print SF1220 Report

Runs the GLSF224P SQRReport process to print theSF1220 report.

SF1219/1220 Report RUN_SF1219 General Ledger, FederalReports, SF224/SF1219/ SF1220, CreateSF1219/1220 File

Runs the GL_1219_1220Application Engine to createa flat file.

Defining the SF224/1220 Report AccountsAccess the SF224/1220 Definition - Accounts page.



SF224/1220 Definition - Accounts page

Effective Date Displays the system date, which you can change.

Status SelectActive.

Range Identify the range of accounts to use for this report and save the page.

See Also

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Setting Up ChartField Attributes, page 533

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,” LinkingAccount Attributes and Values to Account ChartFields, page 544

Defining the SF224/1220 Entry EventsAccess the SF224/1220 Definition - Entry Events page.



SF224/1220 Definition - Entry Events page

Source Trans (transaction),(source transaction)EntryEvent, andCollect/Disburs(collection/disbursement)

Select the source transactions, their associated entry event, and whether eachtransaction is a collection or a disbursement for this report and Save the page.

Defining SF224/1220 Undeposited AccountsAccess the Define SF224/1220 - Undeposited Accounts page.



SF224/SF1220 Definition - Undeposited Accts (accounts) page

From Account andToAccount

Enter a range of undeposited accounts to use on the report. Add asmany rows as necessary to set up the accounts.

Generating SF224/1220 Report DataAccess the Generate SF224/SF 1220 page.

Note. This option generates the data to a table. You must choose a format (hardcopy or flat file) andthen run the report based on your selection using one of the menu options.



Generate SF224/SF1220 Data page

Standard Form SelectSF224prnt(SF224print) orSF1220prntSF1220(print) to print either ofthese reports, or selectSF224 fileto create a flat file of this report.

Business Unit Select the Business Unit for the organization that is submitting this report.

Agency Location Code Select the ALC for the reporting agency.

Calendar ID Select the appropriate calendar to apply to this selected report.

Fiscal Year Select the Fiscal Year to apply to the selected report.

Accounting Period Select the Accounting Period that applies to the selected report.

Accounting Close Date Enter or select the accounting period’s close date.

Disbursing Officer Select the ID of the Disbursing Officer. Select this only for SF1220 reports.

Supplemental Number Use this field to track monthly submission counts. The default value is1. You must modify this number manually if you submit a subsequentadjustment 224 report during the same accounting month.

Run Save the page and click this button to run the SF224/SF1220 SQR ReportGenerate process to update the report staging tables.

Note. You can also print the SF224 report and create a flat file by selecting the Run SF224/CreateFile. You can print the SF1220 report by selecting Run SF1220 Report.



Printing the SF224 Report and Creating the Flat FileAccess the Run SF224 Report/Flat File page.

This page is identical to the Generate SF224/SF1220 page with the exception that youcan only print and create a flat file for SF224.

See Also

Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Generating SF224/1220 Report Data, page 575

Defining the SF1219 ReportAccess the SF1219 Definition page.

SF1219 Definition page

Report Line, Account,Entry Event SourceTransaction, and EntryEvent

Select the values that you want to apply to this report based on eachReport Linethat you add and select.

Printing the SF1219 ReportAccess the Print SF1219 Rpt page.

This page requires the same information as the SF224/SF1220 Generate page. However, thedisbursing officer name is not required and does not appear on the page and you can only print theSF1219 report. After submitting FMS Forms 1219 and 1220, the disbursing officer may submit asupplemental report to adjust data. You can use the Supplemental Number field on the run controlpage to manual increment the number of reports submitted within a given period.



See Also


Printing the SF1220 ReportAccess the Print SF1220 Report page.

This page requires the same information as the SF224/SF1220 Generate page with theexception that you can only print the SF1220 report.

See Also


Creating the SF1219/1220 Flat FileAccess the 1219/1220 Report page.

This page requires the same information as the SF224/SF1220 Generate page including thename of the Disbursing Officer and this officer’s phone number.

See Also


Defining and Generating a Fund BalanceReconciliation Report

To define and generate a Fund Balance Reconciliation report, use the Reconciliation RptDefinition component (FUNDBL_RCN_DEFN).


• Define the general ledger accounts to reconcile.

• Define entry events to reconcile.

• Import the U.S. Treasury data.

• Generate the Fund Balance Reconciliation report.

Understanding Fund Balance Reconciliation ReportingFederal Agencies use the Fund Balance with Treasury (FBWT) account to reconcile with U.S.Treasury’s Financial Management Service (FMS) records. This reconciliation is essential toenhancing internal controls, improving the integrity of various U.S. government financial reports,and providing a more accurate measurement of budget results.



The PeopleSoft Fund Balance Reconciliation processes include the capability to:

• Import the monthly account activity and trial balances, which includes the banking system and any warrantactivity, from the U.S. Treasury and compare it with your agency’s general ledger cash activity.

• Define a reconciliation report that compares your agency’s general ledger accounts and entry eventsthat are required by the reconciliation process with the U.S. Treasury data.

• Generate a Reconciliation Report (GLS9500) that lists of any differences between your agency’s dataand the U.S. Treasury’s data by Fiscal Year, Accounting Period, and TSYMBOL.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Generating the Fund Balance Reconciliation Report, page 581.

Pages Used to Define and Generate the Fund BalanceReconciliation Report


Account Definition FUNDBL_RCN_DEFN1 General Ledger, FederalReports, Fund BalanceReconciliation, DefineReport Definition, AccountDefinition

Enter the General Ledgeraccounts that you want toreconcile with the U.S.Treasury data.

Entry Event Definition FUNDBL_RCN_DEFN2 General Ledger, FederalReports, Fund BalanceReconciliation, DefineReport Definition, EntryEvent Definition

Enter the Entry Event codesand select whether they are acollection or disbursementto reconcile with the U.S.Treasury data.

Import Treasury Files LOAD_FUNDBL_REQ General Ledger, FederalReports, Fund BalanceReconciliation, ImportTreasury Files

Select the GOALS file typeand attach the file containingthe U.S. Treasury data.

Generate ReconciliationReport

RUN_FBRECON_RPT General Ledger, FederalReports, Fund BalanceReconciliation, GenerateReconciliation Report

Enter the data to run thereconciliation process andgenerate the Fund BalanceReconciliation report.

Defining the General Ledger Accounts to ReconcileAccess the Fund Balance Reconciliation - Account Definition page:

Fund Balance Reconciliation - Account Definition page



From Account, To Account Enter one account or a range of accounts that you want to reconcile with theU.S. Treasury’s data. Add rows as needed and Save the page.

Defining Entry Events to ReconcileAccess the Fund Balance Reconciliation - Entry Event Definition page:

Entry Event Definition

Entry Event, CollectionDisbursement

Select the Entry Event code that applies to this reconciliation,and select whether it is a collection or a disbursement. Add entryrows as needed and Save the page.

Importing the U.S. Treasury DataAccess the Import Treasury Files page.

Fund Balance Reconciliation - Import Treasury Files

GOALS File Type(government onlineaccounting link system)

Select the type of file you are importing from the U.S. Treasury GOALS:

• Receipt Account Ledger

• Receipt Account Trial Balance

• Und Appropriation Acct Ledger( Undisbursed AppropriationAccount Ledger)

• Und Appropriation Acct TB( Undisbursed AppropriationAccount Trial Balance)

Save the page.

Attached File Click the Add icon to attach the file in the field.

Click the Delete icon to detach the file. This does not deletethe file from your server.



Click the View icon to open and display the contents of the file. Youmust attach the file before you can view it.

Save the page.

Important! Files must be entered in logical pairs. Account Ledger Activityand Account Trial Balance must be selected for the same data type. Datatype is either Undisbursed Appropriations or Receipts.

Note. These buttons work the same as the buttons on the Load FACTS I Data page.

See Chapter 25, “Federal Government, Statutory, and XBRL Financial Statement Reporting,”Loading MAF and FACTS I Data, page 523.

Generating the Fund Balance Reconciliation ReportAccess the Generate Reconciliation Report page:

Generate Reconciliation Report page

Report Request Parameters Enter the parameters and click the Run button to run theFund Balancewith Treasury Recn (fund balance with treasury reconciliation)process, GLS9500 SQR Reportto compare the data that you definedfor this reconciliation to the U.S. Treasury’s data and produce a reportthat defines any differences in the data.

Configuring the FUND_STATUS PS/nVision ReportFederal government agencies require one or more available funds reports for each TAFS/TASthat is subject to FACTS II reporting requirements.

To configure the FUND_STATUS PS/nVision report, use the Tree Manager component (PSTREEMGR).


• Maintain the FED_RCO2_ACCOUNTS tree.

• Define the FUND_BALANCE nVision report layout.



• Request and distribute the FUND_BALANCE report.

Pages Used to Configure the FUND_STATUS PS/nVision Report


Tree Manager PSTREEMGR Tree Manager, Tree Manager Review an existing tree, treelevels, or a tree definition.

Scope Definition NVS_SCOPE_DEFN Reporting Tools, PS/nVision,Define Scope, ScopeDefinition

Defines the scope forgenerating a PS/nVisionreport.

nVision Report Request NVS_REPORT_RQST Reporting Tools, PS/nVision,Define Report Request,nVision Report Request

Enter the data necessary torun a PS/nVision report.

Maintaining the FED_RC02_Accounts TreeAccount tree FED_RC02_ACCOUNT is delivered specifically for Fund Status reporting. Changes to the tree,including node description, account hierarchy, and so on, are reflected when you execute the nVision report.

FED_RC02_ACCOUNTS Account Rollup tree

SeePeopleTools PeopleBooks: “PeopleSoft Tree Manager”



Defining the FUND_BALANCE nVision Report LayoutThe nVision Layout FUND_STATUS is processed with the Scope definition FUND_STAT whichcontains Fund, Department ID, and Program Code as selection criteria.

PeopleSoft/nVision scope definition FUND_STAT

For each unique combination of Fund, Department and Program values, you can generate an Excelspreadsheet based on the year-to-date balances in the Ledger table.

The following Microsoft Excel worksheet is the fund available information for FundF200, Department 42000, Program P2000.



MicroSoft Excel funds worksheet

It can be viewed at three different levels corresponding to the levels in the FED_RC02_ACCOUNTStree by clicking the 1, 2, or 3 button in the upper left corner of the worksheet.

Level 1 (button 1) shows only the four summarized totals:

• Total Resources

• Fund Distribution

• Spending Activity

• Balances Available

Level 2 (button 2) shows detail line items under each group.

Level 3 (button 3) shows the balances for each accounts, as defined in the account tree.

Requesting and Distributing the FUND_BALANCE ReportAccess the PeopleSoft/nVision Report Request page.



PeopleSoft nVision Report Request

The delivered Report Request creates worksheets named after the Department ID and theProgram Code that you specify in the ‘File Template’ edit box:

%RID%_d%SFV.DEPTID%_p%SFV.PROGRAM_CODE%.xls

Directories named after the Fund names are created, as specified in the ‘Directory Template’ edit box:

Fund_%SFV.FUND_CODE%

Fund Instance

SeePeopleTools PeopleBook: “PS nVision”



Setting Up Federal Reimbursable AgreementAccounts in General Ledger

To set up federal reimbursable agreement accounts in PeopleSoft General Ledger, use theReimbursable Agreement Account component (RMC18_SETUP).

This section describes how to set up reimbursable agreement accounts.

Understanding Federal Reimbursable Accountsin General LedgerFederal agencies and the Department of Defense (DOD) often use reimbursable funding to performwork on behalf of others and then be reimbursed for the work. A reimbursement ID is created basedupon an agreement between agencies or an outside organization. This agreement is negotiated priorto acceptance. Agencies may only bill back the pre-negotiated reimbursable amount, which makes itimperative that they are able to track reimbursable agreements separately from other types of funding,as well as access the current status of the reimbursable amount, billing limit, amount expendedagainst the agreement, and the amounts collected against the agreement.

Federal agencies and the DOD also operate under a revolving fund. Several organizations withinthese two groups operate much a like a business in that they charge for goods and services, and anyproceeds they receive from sales finance the fund. These organizations must be able to bill for goodsand services and track the status of the bills and any collection activity.

PeopleSoft Contracts enables the user to review this information required by the government onthe Reimbursable Agreement Inquiry page. In order to take advantage of this inquiry, you mustset up the Reimbursable Agreement Account information. On this page you define the accountsfor the type of amount in the Reimbursable Agreements inquiry:

• Advanced Amount equals the sum of the amounts in SGL accounts 2310, 5200, and the UnbilledAR account based on the specified search criteria for the inquiry.

• Advanced Remaining Amount equals the sum of SGL account 2310 for the specifiedsearch criteria for the inquiry.

• Billed Amount equals the Advanced Amount less 2310.

• Earned Amount equals the sum of SGL account 5200 for the specified search criteria for the inquiry.

• Unbilled Amount equals the sum of the Unbilled AR account for the specified search criteria for the inquiry.

• Obligated Amount equals the sum of amounts in SGL accounts 4802, 4872, 4882, 4801, 4871,and 4881 for the specified search criteria for the inquiry.

• Expended Amount equals the sum of amounts in SGL accounts 4902, 4972, 4982, 4901, 4971,and 4981 for the specified search criteria for the inquiry.

• Collected Amount equals the sum of amounts in SGL account 1023 for the specifiedsearch criteria for the inquiry.

• Committed Amount



See Also

PeopleSoft Contracts 8.8 PeopleBook, “Managing Contracts”

Pages Used to Set Up Reimbursable Agreement Accounts


Reimbursable AgreementAccount

RMC18_SETUP General Ledger,Federal Reports, DefineReimbursable Account,Reimbursable AgreementAccount page

Set up General LedgerAccount ChartFields foreach of the ReimbursableAgreement Amount Typespredefined for the page.

Setting Up Reimbursable Agreement AccountsAccess the Reimbursable Agreement Account page.

Reimbursable Agreement Account page

Amount Type Select the amount types that appear in the Reimbursable AgreementsInquiry in PeopleSoft Contracts.

Account Select the Account ChartField that applies to each Amount Type. Adescription and example of how the amounts in the inquiry are derivedfor each Amount Type resides in the PeopleSoft Contracts PeopleBook,“Federal Reimbursable Agreements” chapter.

Account Action Select either:Addor Deduct.

This describes the action taken on the detail amount for the account whencombining them into the higher level Amount Type.



See Also

PeopleSoft Contracts 8.8 PeopleBook, “Working with Federal Reimbursable Agreements”

Using PSnVision for Statutory ReportingYou can meet your GASB 34/35 statutory reporting requirements using PSnVision and a PeopleSoft template.

Understanding GASB 34/35 ReportingThe Government Accounting Standards Board (GASB) 34 /35 requires state and local governments,and public colleges and universities to submit basic financial statements. PeopleSoft provides atemplate that enables local and state governments and public colleges and universities to designPSnVision reports that adhere to the GASB 34/35 guidelines.

• Government-wide Statements

A statement of net assets and activities.

• Government Fund Statements

A balance sheet and a statement of revenues, expenditures, and changes in fund balances.

• Proprietary Fund Statements

A statement of net assets, a statement of revenues, expenditures, and changes in fundbalances, and a statement of cash flows.

• Fiduciary Fund Statements

A statement of fiduciary net assets and a statement of changes in fiduciary net assets.

• Budget Comparison Statements

The original budget, the final appropriated budgets for the reporting period, and the actual inflows,outflows, and balances stated on the government’s budgetary basis.

Using XBRL to Produce Balance Sheets andIncome Statements

To use XBRL to produce balance sheets and income statements, use the following components:

• XBRL Context (XBRL_CONTEXT)

• XBRL NameSpace (XBRL_SETUP_NSPACE)

• XBRL Element (XBRL_ELEMENT)

• XBRL Instance Template (XBRL_SETUP)

This section provides an overview of the production of XBRL (eXtensible Business ReportingLanguage) balance sheets and income statements and discusses how to:



• Set up supporting trees and ChartField value sets.

• Specify the XBRL context.

• Specify a NameSpace Alias for the NameSpace URL.

• Define the XBRL elements.

• Set up the XBRL Instance template.

• Define the elements for the instance template.

• Create XBRL Instance.

Understanding XBRL Financial StatementsXBRL is a royalty-free, open specification software that uses XML data tags to prepare andpublish information. PeopleSoft supports XBRL 2.0 specifications.

It is particularly appropriate to the presentation of financial reports on the Internet and acrosssoftware products. XBRL reports also reduce the risk of data entry error by eliminating the needto manually key information for different venues and formats.

PeopleSoft enables you to create balance sheets and income statements in XBRL that conformsto the XBRL schema and taxonomies for US GAAP.

An XBRL schema is the core low-level component of XBRL and consists of the physicalXSD and DTD (Document Type Definition) files that express how instance documents (yourfinancial statements and their taxonomies) are to be built.

An XBRL taxonomy is a vocabulary or dictionary of elements created by a regulatory group or governing bodyusing XBRL specifications that enables the particular group to ensure exchange of business information in apredefined consistent manner. Taxonomies are derived from accounting rules governing how financial data isdisclosed in different countries or jurisdictions. The taxonomies discussed in this topic refer to the US GAAPtaxonomies and the approximately 600 monetary elements used for the production of balance sheets andincome statements. The documentation also assumes that you have a thorough working knowledge of XBRL.

The following are the general activities necessary to produce and distribute yourreports using PeopleSoft functionality:

• Store the parts of taxonomies representing numeric facts in the database.

• Generate reports conforming to the taxonomies.

• Distribute the reports to the appropriate users.

You store taxonomies and their elements in PeopleSoft tables. After creating the elements, youpopulate the elements using ChartField Value Sets. You then create ChartField Value Sets todefine the accounts that determine taxonomy element. PeopleSoft creates Balance Sheets andIncome Statements with only the numeric facts of taxonomies.

Balance sheets and income statements are created as XBRL instance (in form of a message) for a businessunit r— ledger group using PeopleSoft Application Engine (GL_XBRL) and PeopleSoft XMLDOC.

When you run your balance sheet and income statement reports, you distribute themusing PeopleSoft Integration Broker.

See http://www.xbrl.org/



Pages Used to Produce Financial Statements Using XBRL


XBRL Context XBRL_CONTEXT General Ledger, XBRL Define XBRL numericcontexts and specify theirEffective Date and Status.PeopleSoft supports onlynumeric context. An XBRLContext can specify reportsfor amounts or amountsper share.

NameSpace Setup XBRL_SETUP_NSPACE General Ledger, XBRL,NameSpace

Define a NameSpace aliasfor the NameSpace URLthat provides access to thetaxonomies, which areappropriate to your XBRLreports.

XBRL Element XBRL_ELEMENT General Ledger, XBRL,Element

Specify the XBRL labels andelements to be used in theproduction of your reports.

Setup XBRL_SETUP_TYPE General Ledger, XBRL,Instance Template

Define the template nameand specify the scope, entityinformation, and time spanfor your reports.

Instance Element XBRL_RPT_ELEMENT General Ledger, XBRLInstance Template

Specify the elements andChartField Value Sets thatdetermine the items andamounts reported.

Create XBRL Instance RUN_XBRL General Ledger, XBRL,Create Instance

Determine the dates, thereport template used, and thebusiness unit or ledger setthat are used to create yourreports.

Setting Up Supporting Trees and ChartField Value SetsInitially, determine the XBRL taxonomies and elements necessary to produce the items that make up yourreports. To supply the monetary values that are to be reported, create PeopleSoft trees and ChartField value sets.

You might be able use existing trees and associated ChartField value sets that you previouslycreated for the closing of the books for your reporting entity.

SeePeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “Defining and UsingChartFields,” Defining and Using ChartField Value Sets.

SeePeopleTool PeopleBooks: PeopleSoft Tree Manager

Specifying the XBRL ContextAccess the XBRL Context page.



XBRL Context page

Context Name Use this page to enter one or more context IDs to be used by the XBRLelements to create balance sheets and income statements or individual itemsconstituting those statements either for amount or amount per share.

Context Type This is a display only field. PeopleSoft supports the Numericparts of the taxonomies.

XBRL Unit Specify if the XBRL Context is to be used to report for the CurrencyAmount or Amount Per Share.

Description Provides a description of the context.

Specifying a NameSpace Alias for the NameSpace URLAccess the XBRL NameSpace page.

XBRL NameSpace page

NameSpace Alias Enter a namespace alias to be used for an XBRL instance to specifythe NameSpace URL used to produce your reports.

NameSpace Contains the URL where the taxonomy elements are specificfor your XBRL reports.

Defining the XBRL ElementsAccess the XBRL Element page.



XBRL Element page

Element Label Enter a label to identify the XBRL element. The label will be used torepresent the element in XBRL template page.

XBRL Element ID Enter the name of the XBRL element available to the specified Element Labelthat is to be used in you report instance when you produce your reports.

NameSpace Alias Enter the alias for the NameSpace (URL) where the elements andtaxonomies are located for your reports.

Context Enter the context you previously defined. PeopleSoft supportsnumeric context only.

Setting Up the XBRL Instance TemplateAccess the XBRL Report Template Setup page.



XBRL - Setup page

XBRL Report Template Enter a name for the report template.

Single Business Unit Click if the template is for a single business unit. If this check box is notselected, the system assumes that there are multiple business units.

Identifier Scheme URL Enter the URL for the authority governing the Entity Identifier. For example,the NASDAQ URL is entered when the Entity Identifier Override is the stocksymbol for the entity. The information provided by the NASDAQ web siteprovides identification for the reports appropriate for investors.

Entity Identifier Type Select either Business Unit or Override. If you select Business Unitentity information is provided from PeopleSoft tables. When youselect Override, you must provide the standard symbol and the URL tothe governing body for that entity symbol.

SetID Enter the SetID for the TimeSpan you specify.

TimeSpan Enter the TimeSpan appropriate to the closed period for which you arereporting. The As of Date you enter on the report request is used to establishthe time frame of the financial statements with the Time Span you specifyhere. This means that the As of Date on the report request page mightnot be the as of date on the balance sheet, which will be the end date ofthe last closed accounting period within the time frame.

Defining the Report Elements for the Instance TemplateAccess the Report Element page.



XBRL Report Element page

ChartField Value Set SetID Select the SetID to be used for prompting of ChartField Value Sets forindividual elements that you include on this page.

Element Label Select the labels for XBRL element that are to be include in the template.

Include Click to include the Element Labels in your report. Once this checkbox is selected, the ChartField value set is required.

ChartField Value Set Select the set that defines the scope of ChartField criteria from whichamounts are rolled up to your report.

XBRL Element ID Displays the related XBRL Element ID for the element.

Running XBRL ReportsAccess the Create XBRL Report page.



Create XBRL Report page

As of Date Establishes the time frame of the financial statements in conjunction withthe Time Span you enter on the report template.

Note. The As of Date on the report request page might not be the asof date on the balance sheet, which will be the end date of the lastaccounting period within the time frame.

Report Template Enter the template for the report you are creating.

Currency Code Displays either the base currency of the ledger or the currency of the ledger set.

Business UnitandLedger Select these values only if you specified reporting from a singlebusiness unit on the report template.

Ledger Set Select a value if you are reporting on several business units withinthis ledger set. The ledger set contains the business units and ledgerfrom which the financial statement is generated.




APPENDIX A

Configuring Batch Processes

This appendix discusses how to configure temporary tables for batch processing.

Configuring Temporary Tables for Batch ProcessingWhen you run batch processes in parallel, you risk data contention and deadlocks on temporary tables.To avoid this, PeopleTools enables you to dedicate specific instances of temporary tables for eachprocess. When PeopleSoft Application Engine manages a dedicated temporary table instance, it controlsthe locking of the table before use and the unlocking of the table after use.

When you decide how many temporary table instances to dedicate for a process, consider the numberof temporary tables that the process uses. More instances result in more copies of the temporarytables on the system. For example, if a process uses 25 temporary tables and you have 10 instancesfor a process, you will have 250 temporary tables on the system.

If you run processes in parallel and all of the dedicated temporary table instances are in use, the performanceof the process decreases. You need to find a balance that works for your organization.

Note. When you specify the number of instances, PeopleSoft Application Designer displays a list of thetemporary tables for the process. Use the list to determine how many temporary tables each process uses.

Specify how many temporary table instances to dedicate for each of the following batch processesthat can run in parallel in PeopleSoft General Ledger:

• Allocations (FS_ALLC)

• Combo Edit Build (FS_CEBD)

• ChartField Combination Editing (FS_CEDT_PROC)

• Journal Generator (FS_JGEN)

• Ledger Archive (GL_ADB_ARCH)


• Post Daily Balance (GL_ADB_POST)

• Spreadsheet Journal Import (GL_EXCL_JRNL)

• Journal Edit (GL_JEDIT)

• Journal Archive (GL_JRNL_ARCH)

• Journal Copy (GL_JRNL_COPY)


Configuring Batch Processes Appendix A

• Flat File Journal Import (GL_JRNL_IMP)

• Flat File Ledger Import (GL_LED_IMP)

• Ledger Load (GL_LED_LOAD)

• Standard Journal Entry (GL_SJE)

• Commitment Control Budget Closing (FSPYCLOS)

• Commitment Control Budget Post (FSPQPOST)

• Commitment Control Budget Processor (FSPKBDP3)

• Commitment Control Archive (FS_KKAR)

• Commitment Control Notification (KK_NTFY_WF)

• Closing (GLPCLOSE)

• Consolidations (GLPOCONS)

• Equitization (GLPQEQTZ)

• Journal Post (GLPPPOST)

• Multicurrency Processing (FSPCCURR)

• Open Item Reconciliation (GLPPOITM)

• Summary Ledger (GL_SUML)

Note. The processes listed here are the main GL processes (AE or COBOL). PeopleSoft General Ledger alsohas some AE or SQR processes that are mainly for loading data to do government reporting ( FACTS I,FACTS II, SFxxx). Since these are more like a report than a process, they are not included in this list.

The PeopleTools documentation discusses the usage of temporary tables in detail anddescribes how to specify the number of instances.

If you run any of the PeopleSoft General Ledger AE or COBOL processes, also configure the temporary tablesfor those processes. ThePeopleSoft General Ledger PeopleBookdiscusses how to do this in detail.

See Also

PeopleTools PeopleBook: PeopleSoft Application Engine

Chapter 7, “Optimizing General Ledger Performance,” page 79


APPENDIX B

Delivered Workflows for PeopleSoftGeneral Ledger

This appendix discusses the Journal Processing workflow for PeopleSoft General Ledger.

See Also

PeopleTools PeopleBook: PeopleSoft Workflow

PeopleTools PeopleBook: Using PeopleSoft Applications

Delivered Workflows for PeopleSoft General LedgerThis section discusses PeopleSoft General Ledger workflows. The workflows arelisted alphabetically by workflow name.

Journal Entry ApprovalThis section discusses the Journal Entry Approval workflow.

Description

Event Description Further Approval Required.

Action Description Generates a worklist entry for the next user in the approval hierarchy.

Notification Method Email and Worklist

Workflow Objects

Approval Rule Set JOURNAL_ENTRY_APPROVAL

Business Process JOURNAL_ENTRY_APPROVAL

Activity APPROVE_DENY_JOURNAL

Role SUPERVISOR

Journal Entry DenialThis section discusses the Journal Entry Denial workflow.


Delivered Workflows for PeopleSoft General Ledger Appendix B

Description

Event Description Journal Entry denied.

Action Description Sends an email to the previous user.


Workflow Objects




Role SUPERVISOR and/or MANAGER(S)

Journal Entry ApprovalThis section discusses the Journal Entry Approval workflow.

Description

Event Description Generates a worklist entry for the next user in the approval hierarchy.

Action Description The system routes work items to the appropriate user’s worklist.


Workflow Objects




Role SUPERVISOR and/or MANAGER(S)


APPENDIX C

PeopleSoft General Ledger Reports

This appendix provides an overview of PeopleSoft General Ledger reports and enables you to:

• View summary tables of all reports.

• View report details.

Note. For samples of these reports, see the Portable Document Format (PDF) fields thatare published on CD-ROM with your documentation.

See Also

PeopleTools PeopleBook: Process Scheduler

PeopleSoft General Ledger ReportsThis table lists the PeopleSoft General Ledger reports, sorted alphanumerically by report ID. If you needmore information about a report, refer to the report details at the end of this appendix.

Report ID and ReportName

Description Navigation Run Control Page

FIN1001Message Log Report

Prints message logs for aprocess instance ID and batchreport type, similar to theonline query available foreach background program.Displays job ID, programname, date, time, sequencenumber, logged message, andexplanation for each processinstance ID. (SQR)

General Ledger, MonitorBackground Processes,Background Process Report

RUN_FIN1001


PeopleSoft General Ledger Reports Appendix C



FIN2001Journal Entry Detail Report

Displays all journal entriesentered in the system fora business unit and ledgerwithin the date rangespecified. Prints the journalentries in ascending IDorder within the ledger andshows the journal date, thesource, whether a reversalentry was created, journalstatus, posted date (if any),and a description. For eachline included in the journalentry, lists the line numberof the entry, the accountnumber, a description,the department, product,and project ChartFieldvalues, and debit and creditdetail. Also prints statisticalinformation where includedin a journal entry. (SQR)

General Ledger, GeneralReports, Journal Entry Detail

RUN_FIN2001

FIN2005Journal Entry Detail Reportwith Attributes

This report is similar to theJournal Entry Detail Report,except this report also liststhe ChartField attributevalues. (SQR)

General Ledger, GeneralReports, Journal Entry withAttributes

RUN_FIN2005

FIN5001Reconciliation by SystemSource

This report consists ofdetailed subsystem and GLjournal transactions that areaggregated to the businessunit, subsystem source,ledger, account or alternateaccount, fiscal year andaccounting period level.

For example, it lists the dataat the system source level,such as AP, and then lists allthe activity for AP, includingwhat was posted and notposted, for one or moreselected ChartFields thatappear in the data that youloaded. (SQR)

General Ledger, GeneralReports, GL ReconciliationSubsystem, Reconciliationby System Srce (source)

RUN_FIN5001


Appendix C PeopleSoft General Ledger Reports



FIN5005Reconciliation by ChartFieldreport.

This report lists the databased on one or moreselected ChartFields thatappear in the data thatyou loaded. Each of thesubsystem amounts thatfall within the ChartFieldcombination is listed on thereport along with the totalamounts for the ChartFieldsand the related ledgers.(SQR)

General Ledger,General Reports, GLSubsystem Reconciliation,Reconciliation byChartFields

RUN_FIN5005

GLC1000Summary Ledger DefinitionReport

Displays information aboutsummary ledgers, includinga description, the detailledger it summarizes, recordnames, and a listing of theChartFields associated withthe ledger. (Crystal)

General Ledger, SummaryLedgers, Summary LedgerDefinition Rpt (report)

RUN_GLC1000

GLC4001Summary Calendars

Displays information aboutsummary calendars. Includesa description as well as alisting of the periods youhave defined for the calendar.(Crystal)

Setup Financials/SupplyChain, Common Definitions,Calendars/Schedules,Summary Calendar Report

RUN_GLC4001

GLC4003Combination Group

Displays information onChartField combination editgroups for a selected setID.(Crystal)

Setup Financials/SupplyChain, Common Definitions,Design ChartFields,Combination Editing,Combination Group Report

RUN_GLC4003

GLC4008Journal Class Report

Displays journal class nameand a description of each fora selected SetID. (Crystal).

Set Up Financials/SupplyChain, Common Definitions,Journals, Class Report,Journal Class Report

RUN_GLC4008

GLC5501ADB Calculation Report

Lists ADB calculation detailsincluding averaged period,date, and time. (Crystal)

General Ledger, AverageDaily Balance, ADBCalculation Report

RUN_GLC5501

GLC6001Allocation Group

Lists detail informationassociated with a particularallocation group. (Crystal)

Allocations, Reports,Allocation Group

RUN_GLC6001





GLC7501Journal Entry Detail

Shows journal entry detailinformation by business unit,journal ID, date, description,ledger group, source,reversal, foreign currency,rate type, effective date,and effective rate. It alsoshows line number, account,description, amount, ratetype, exchange rate, foreignamount, base amount,and totals for the journal.(Crystal)

General Ledger, Journals,Journal Entry, Create JournalEntries, Journal Entry LinesPage, Select Print Journalvalue in the Process field,and click Process button.

RUN_GLC7501

GLS1001Summary Ledger Detail

This is a template fordesigning reports basedon user-specific ledgerdefinitions. This is basedon the summary ledger(PS_S_LEDGER_SUM),which you can find in theDEMO database. The recorddefinition set consists of thefollowing ChartFields:ACCT, OPERATING_UNIT,DIVISION,PRODUCT_AREA, andPROJ. Contains one statisticscode field named STATS.(SQR)

General Ledger, SummaryLedgers, Summary LedgerDetail Report

RUN_GLS1001

GLS1002Closing Rules

Displays information aboutclosing set rules. It printsa description of the closeset, identifies the name ofthe account ChartField, andshows the ChartField towhich that profit and lossaccount will be closed.Also shows the option forretaining earnings into theChartField. (SQR)

General Ledger, CloseLedgers, Closing RuleReport

RUN_GLS1002

GLS1003Closing Trial Balance

Summarizes all entries onthe ledger by account type.Prints beginning and endingbalances for the year, totalsfor the period, adjustments,and closing entries. (SQR)

General Ledger, CloseLedgers, Closing TrialBalance

RUN_GLS1003

GLS1004Journal Closing Status

Displays the journal linedetails for journal lines withvarious closing statuses.(SQR)

General Ledger, CloseLedgers, Journal ClosingStatus Report

RUN_GLS1004





GLS1005Translate LedgerReconciliation

This report reconciles theamounts in the currencytranslation ledger to theamounts in the primaryledger within a Multibookledger group. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translate Ledger Reconcile

RUN_GLS1005

GLS1006Ledger In-Sync

This report searches thecurrency translation ledgerwithin a multibook ledger tosee if there is any data (for aparticular year) violating therequired ledger structure.(SQR)

General Ledger, ProcessMulti-Currency, Reports,Ledger In-Sync

RUN_GLS1006

GLS2000Elimination Set Definition

Displays all elimination setdefinitions for financialconsolidations. Listsaccounts to whichdifferences will post if theset doesn’t eliminate andshows the ChartFields(such as ACCOUNT andBUSINESS_UNIT) and theChartField values that makeup the elimination set, aswell as a description of thosevalues. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets

RUN_GLS2000

GLS2001Minority Interest SetDefinition

Displays the minority interestset definitions for financialconsolidations. Lists foreach minority interest set adescription, tree structure ID,the subsidiary entity, andpercent of ownership. Alsolists the accounts to whichdifferences will post if the setdoesn’t eliminate, as wellas the ChartField, mannerspecified, tree name/level,and the values that makeup the parent/subsidiaryaccounts. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Minority Interest Sets

RUN_GLS2001





LS2002Consolidation Set Report

Displays the options andcontrols that tell GeneralLedger how to processa consolidation. Lists thejournal ID mask, source,and relative eliminationreversal date for eliminationsjournals, the ChartFieldsincluded in the eliminationjournals, whether or not allelimination sets defined forthe consolidation tree willapply, which eliminationsets will be used, whether allminority interest sets apply,and which minority interestsets will be used. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Consolidation Definition,Consolidation Set Report

RUN_GLS2002

GLS2003Consolidation Out ofBalance Report

Displays the eliminationsets and ledger amountsprocessed for a consolidationrequest. The elimination setsare totaled and any out ofbalance amount is displayed.The out of balance amountsare also summarized at thenode and tree levels. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Out of Balance,Consolidation Out ofBalance Report

RUN_GLS2003

GLS2004Minority InterestEliminations andAdjustments

Displays the results ofminority interest calculationsfor a consolidation requestbased on the combinationof business units present inthe consolidation tree. Theelimination and adjustmententries are grouped byminority interest set. (SQR)

General Ledger,Consolidate FinancialData, Reports, Minority IntElim/Adjustment

RUN_GLS2004

GLS2005Audit Elimination Sets

Displays the eliminationsets and audit informationincluding account andbusiness unit. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets Audit,Audit Elimination Sets

RUN_GLS2005

GLS2006Equitization Rules

Displays the definitioninformation and purposefor the equitization ruleincluding component,ChartField, value, anddescription. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Equitization Rules

RUN_GLS2006

GLS2007Subsidiary Ownership SetsReport

Shows the ownership,set status, effectivedate, description, entityChartField, subsidiaryentity, parent, ownershippercentage, and controllingequitize. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Ownership Sets, SubsidiaryOwnership Sets Report

RUN_GLS2007





GLS2008Equitization Calculation Log

Lists equitization calculationdetails by process instance.(SQR)

General Ledger, ConsolidateFinancial Data, Reports,Equitization Calculation Log

RUN_GLS2008

GLS3000Open Item Listing

Lists Open Items for theaccounts specified, includinga description of the accounts,the OpenItem key field, and adetailed listing of the journallines that have an open statusup to the As of Date. Thejournal lines are subtotaledby key field value. Journallines containing OpenItemaccounts are matchedtogether based on theOpenItem edit field. (SQR)

General Ledger, Open Items,Open Item Listing Report

RUN_GLS3000

GLS3001InterUnit Activity

Displays reconciliationinformation by businessunit, ChartField, primaryand balancing values, andvariance. (SQR)

General Ledger, GeneralReports, InterUnit Activity

RUN_GLS3001

GLS4000Schedules

Prints a list of the schedulesyou have defined for aSetID. The report includes adescription of each scheduleand the definition of itsfrequency. (SQR)

Setup Financials/SupplyChain, Common Definitions,Calendars/Schedules,Schedules Report

RUN_GLS4000

GLS4002Combination Rule

Displays information ona selected ChartFieldcombination edit rule. (SQR)

Setup Financials/SupplyChain, Common Definitions,Design ChartFields,Combination Editing,Combination Rule Report

RUN_GLS4002

GLS5000Translation Definition

Displays the details andrules of each currencytranslation step. For eachtranslation step, the reportshows the description, ledgerinformation, output andjournal options, and gain andloss ChartKeys. In addition,detailed informationis displayed for everytranslation rule used by thetranslation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation Step, TranslationStep Definition Report

RUN_GLS5000





GLS5001Revaluation Definition

Displays the details of eachcurrency revaluation step,including revaluation stepdescription, ledger andTimeSpan information,exchange rate type, outputand journal options, gain andloss ChartKeys, and detailedrevaluation ChartKeyinformation. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Revaluation Step,Revaluation Step DefinitionReport

RUN_GLS5001

GLS5002Translation Calculation Log

Lists translation calculationdetails by process instanceand translation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation Calculation Log

RUN_GLS5002

GLS5003Revaluation Calculation Log

Lists revaluation calculationdetails by process instanceand revaluation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Revaluation Calculation Log

RUN_GLS5003

GLS5004Translate in LedgerCalculation Log

Lists translation withinledger calculation details byprocess instance and translatewithin ledger step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger CalcLog (translation in ledgercalculation log)

RUN_GLS5004

GLS5005Translation in Ledger

Displays the details and rulesof each translation stepwithin the ledger calculationlog. For each step, the reportshows the description, ledgerinformation, output andjournal options, and gain andloss ChartKeys. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger

RUN_GLS5005

GLS5500ADB Definition report(average daily balancedefinition)

Prints ADB details includingdescription, purpose, andChartField information.(SQR)

General Ledger, AverageDaily Balance, ADBDefinition Report

RUN_GLS5500

GLS6000Allocation Step Report

Lists detailed information forallocation steps. (SQR)

Allocations, Reports,Allocation Step

RUN_GLS6000

GLS6002Allocation Calculation Log

Lists the allocationcalculations that wereperformed for a givenprocess step within aspecified process instance.Displays the pool, basis, andtarget amounts. (SQR)

Allocations, Reports,Allocation Calculation Logs

RUN_GLS6002





GLS6003Budget Copy CalculationLog

Lists the Budget CopyProcess calculations thatwere performed for a givenprocess step within aspecified process instance.For each process step, thereport shows the sequence,business unit, account,department, product, projectstatus, year, period, poolamount, basis amount, basistotal, target amount, andoffset amount. (SQR)

General Ledger, MaintainStandard Budgets, BudgetCopy Calculation Log

RUN_GLS6003

GLS7001Standard Journals report

Lists standard journal entriesand their status. (SQR)

General Ledger, GeneralReports, Standard Journals

RUN_GLS7001

GLS7002Ledger Activity report

Lists the beginning andending ledger balances byChartField combination andaccount. Also lists thedetailed journal line activityposted against the ledger forthe accounting periods thatare specified. (SQR)

General Ledger, GeneralReports, Ledger Activity

RUN_GLS7002

GLS7003Ledger Summary Report

Summarizes journaltotals within a ledger byChartField.

General Ledger, GeneralReports, Ledger Summary,Ledger Summary Report

RUN_GLS7003

GLS7009Posted Journal Summary

Provides the ability toreport on journals postedduring a specific run of theJournal Post process. TheJournal Post process updatesall journals posted with thevalue of the Process Instance.The Process Instance is partof the search criteria that isused by the Posted Journals -Summary report. (SQR)

General Ledger, Journals,Process Journals, PostedJournal Summary Report

RUN_GLS7009

GLS7010Ledger vs Journal Integrity

Checks for any discrepancybetween Ledger and Journaltables within a specifiedperiod range. (SQR)

General Ledger, GeneralReports, Ledger vs JournalIntegrity

RUN_GLS7010

GLS7011Journal Edit Errors

Provides detailedinformation about journaledit errors: period, journalID, date, source, referencenumber, error type, line, linedescription, field name, anderror message. (SQR)

General Ledger, Journals,Process Journals, JournalEdit Errors Report

RUN_GLS7011





GLS7012Trial Balance

Combines detail andsummary balanceinformation. Shows theending ledger balances forthe specified year and periodby ChartField combination.Also displays subtotals byChartField. Prints a finaltotal for debits and credits.(SQR)

General Ledger, GeneralReports, Trial Balance

RUN_GLS7012

GLS7015Journal Suspense Activity

Provides detailedinformation about suspendedjournals. (SQR)

General Ledger, Journals,Suspense Correction,Suspended Activity Report

RUN_GLS7015

GLS7016Ledger Activity withAttributes Report

Lists the journal activity andthe associated attributesfor one or more specificChartFields in a ledgerfor one or more periods,including beginning andending balances. (SQR)

General Ledger, GeneralReports, Ledger Activitywith Attributes, LedgerActivity with AttributesReport

RUN_GLS7016

GLS7017Ledger with Attributes

Generate a FACTS II reportfor a specific business unit,ledger, fiscal year, periodrange, adjustment periodinformation, and FACTS treegroup. You may also indicatethat the numeric field can be23 integers and 3 decimalplaces long. (SQR)

General Ledger, FederalReports, FACTS II Reports,Ledger with AttributesReport

RUN_GLS7017

GLS7500Ledger File Creation

Reads all entries on theledger and gives the endingbalance for the year andperiod by account. Output isrouted to an ASCII file in thespecified format. (SQR)

General Ledger, Ledgers,Export Ledger Data

RUN_GLS7500

GLS8012Journal Line/AccountingEntry Reconciliation

Compares journal entry lineswith accounting entries.(SQR)

General Ledger, GeneralReports, JournalLine/Acctg Reconcil(journal line/accountingreconciliation)

RUN_GLS8012

GLS8310FACTS I Validation report

This report is generatedwhen you run the FACTSI Validation process. Itdescribes any outstandingissues for each FACTS I editthat is run for your FACTS Iaccumulated data. (SQR)

General Ledger, FederalReports, FACTS I, GenerateFACTS I

RUN_CNTL_FACTSI





GLS8311FACTS I Trial Balancereport

This report displays the statusof the General Ledgeraccount balances alongwith the correspondingUSSGL account attributesbased on each TreasurySymbol. (SQR)


RUN_CNTL_FACTSI

GLS8312FACTS II Trial Balance


General Ledger, FederalReports, FACTS II, FACTSII Reports, FACTS II TrialBalance

F2_RUN_GLS8312

GLS8400SF224 Transaction Report

This is a monthly reportsent to the U.S. Treasurythat identifies the dollaramounts of confirmedU.S. disbursements andcollections for an agency byAgency Location Code andfiscal month. This report isused to ensure agreementbetween the agency’srecords of disbursement andcollections and those of theU.S. Treasury. (SQR)

General Ledger, FederalReports, SF 224/ 1219/1220,SF 224 Transaction Report

RUN_GLS8400

GLS8500Federal Trial Balance report

This is a summary trialbalance report. This reportdisplays a beginningbalance, the total amount ofdebits and credits and anending balance. The data isgenerated for the specifiedChartField combination forthe fiscal year , accountingperiods, and adjustmentperiods. This report alsodisplays subtotals byChartField and grand totalsby TAS/TAFS levels. (SQR)

General Ledger, FederalReports, Federal TrialBalance

RUN_GLS8500

GLS8501Federal Transaction Register

This is an online report thatdisplays values at the fund,department, and TAS/TAFSlevels for each accountingperiod along with eachChartField’s attributes andattribute values. (SQR)

General Ledger, FederalReports, Federal TransactionRegister

RUN_GLS8501





GLS9500Fund Balance Reconciliation

This report is run afteryou run the Fund BalanceReconciliation processwhich compares accountactivity and trial balancedata imported from the U.S.Treasury contains to a federalagency’s cash activity. Itcontains any differencesbetween a federal agency’sand the U.S. Treasury’sdata. (SQR)

General Ledger, FederalReports, Fund BalanceReconciliation, GenerateReconciliation Report

RUN_FBRECON_RPT

SF224Statement of CashTransactions

SF224 is a monthly reportto the U.S. Treasury thatidentifies the dollar amountsof confirmed disbursementsand collections by TreasurySymbol, Agency LocationCode, and fiscal month. Thisreport is used by the U.S.Treasury to ensure that theagency agrees with theinternal U.S. agencies thatperform disbursementsthrough the U.S. Treasury.This option enables you tocreate a flat file of the reportto submit electronicallythrough GOALS, and to printa hard-copy of the report.

General Ledger, FederalReports, SF224 / 1219/ 1220,Run SF224 Report/CreateFile

RUN_SF224_SF1220

GLS8400SF224 Statement of CashTransaction Details

This is a monthly reportthat includes the detailtransactions that make upthe totals on the SF224- Statement of CashTransactions report.

General Ledger, FederalReports, SF224 / 1219/ 1220,SF224 Transaction Report

RUN_GLS8400





SF1219Statement of Accountability

This report is used todetermine the accountabilityof disbursing officers forfunds held outside theDepartment of Treasury(cash on hand) by U.S.Treasury Regional FinanceCenters (RFCs) and othernonmilitary agenciesthat do not do their owndisbursing. This option printsa hard-copy version ofthis report. This report isvery similar to the SF1220report. These two reports aretreated as one report whensubmitted electronically andprocessed by GOALS usingthe SF1219/1220 Createoption to create the file.

General Ledger, FederalReports, SF224/ 1219/ 1220,Run SF1219 Report

RUN_GLSF1219

SF1220Statement of TransactionsAccording toAppropriations, Funds, andReceipt Accounts report

Provides the U.S. Treasurywith a monthly statement ofpayments and collectionsperformed by agencies thatdo their own disbursing. Thisoption prints a hard-copyversion of this report. Thisreport is very similar to theSF1219 report. These tworeports are treated as onereport when submittedelectronically and processedby GOALS using theSF1219/1220 Create optionto create the file.


RUN_SF224_SF1220

See Also

PeopleSoft 8.8 Setting Up and Using Commitment Control PeopleBook, “PeopleSoftCommitment Control Reports”

PeopleSoft 8.8 Application Fundamentals for Financial Management Solutions, EnterpriseService Automation, and Supply Chain Management PeopleBook, “PeopleSoft ApplicationFundamentals for FIN, ESA, and SCM Reports”

PeopleSoft Global Options and Reports 8.8 PeopleBook, “PeopleSoft Financial Global Reports”




Glossary of PeopleSoft Terms

absence entitlement This element defines rules for granting paid time off for valid absences, such as sicktime, vacation, and maternity leave. An absence entitlement element defines theentitlement amount, frequency, and entitlement period.

absence take This element defines the conditions that must be met before a payee is entitledto take paid time off.

accounting class In PeopleSoft Enterprise Performance Management, the accounting class defines howa resource is treated for generally accepted accounting practices. The Inventoryclass indicates whether a resource becomes part of a balance sheet account, such asinventory or fixed assets, while the Non-inventory class indicates that the resource istreated as an expense of the period during which it occurs.

accounting date The accounting date indicates when a transaction is recognized, as opposed to the datethe transaction actually occurred. The accounting date and transaction date can be thesame. The accounting date determines the period in the general ledger to which thetransaction is to be posted. You can only select an accounting date that falls within anopen period in the ledger to which you are posting. The accounting date for an itemis normally the invoice date.

accounting split The accounting split method indicates how expenses are allocated or divided amongone or more sets of accounting ChartFields.

accumulator You use an accumulator to store cumulative values of defined items as they areprocessed. You can accumulate a single value over time or multiple values overtime. For example, an accumulator could consist of all voluntary deductions, or allcompany deductions, enabling you to accumulate amounts. It allows total flexibilityfor time periods and values accumulated.

action reason The reason an employee’s job or employment information is updated. The actionreason is entered in two parts: a personnel action, such as a promotion, termination, orchange from one pay group to another—and a reason for that action. Action reasonsare used by PeopleSoft Human Resources, PeopleSoft Benefits Administration,PeopleSoft Stock Administration, and the COBRA Administration feature of theBase Benefits business process.

action template In PeopleSoft Receivables, outlines a set of escalating actions that the system or userperforms based on the period of time that a customer or item has been in an actionplan for a specific condition.

activity In PeopleSoft Enterprise Learning Management, an instance of a catalog item(sometimes called a class) that is available for enrollment. The activity definessuch things as the costs that are associated with the offering, enrollment limits anddeadlines, and waitlisting capacities.

In PeopleSoft Enterprise Performance Management, the work of an organization andthe aggregation of actions that are used for activity-based costing.

In PeopleSoft Project Costing, the unit of work that provides a further breakdown ofprojects—usually into specific tasks.

In PeopleSoft Workflow, a specific transaction that you might need to perform in abusiness process. Because it consists of the steps that are used to perform a transaction,it is also known as a step map.


Glossary

agreement In PeopleSoft eSettlements, provides a way to group and specify processing options,such as payment terms, pay from a bank, and notifications by a buyer and supplierlocation combination.

allocation rule In PeopleSoft Enterprise Incentive Management, an expression within compensationplans that enables the system to assign transactions to nodes and participants. Duringtransaction allocation, the allocation engine traverses the compensation structurefrom the current node to the root node, checking each node for plans that containallocation rules.

alternate account A feature in PeopleSoft General Ledger that enables you to create a statutory chartof accounts and enter statutory account transactions at the detail transaction level, asrequired for recording and reporting by some national governments.

AR specialist Abbreviation forreceivables specialist.In PeopleSoft Receivables, an individual inwho tracks and resolves deductions and disputed items.

arbitration plan In PeopleSoft Enterprise Pricer, defines how price rules are to be applied to the baseprice when the transaction is priced.

assessment rule In PeopleSoft Receivables, a user-defined rule that the system uses to evaluate thecondition of a customer’s account or of individual items to determine whether togenerate a follow-up action.

asset class An asset group used for reporting purposes. It can be used in conjunction with the assetcategory to refine asset classification.

attribute/value pair In PeopleSoft Directory Interface, relates the data that makes up an entry in thedirectory information tree.

authentication server A server that is set up to verify users of the system.

base time period In PeopleSoft Business Planning, the lowest level time period in a calendar.

benchmark job In PeopleSoft Workforce Analytics, a benchmark job is a job code for which there iscorresponding salary survey data from published, third-party sources.

book In PeopleSoft Asset Management, used for storing financial and tax information, suchas costs, depreciation attributes, and retirement information on assets.

branch A tree node that rolls up to nodes above it in the hierarchy, as defined in PeopleSoftTree Manager.

budgetary account only An account used by the system only and not by users; this type of account doesnot accept transactions. You can only budget with this account. Formerly called“system-maintained account.”

budget check In commitment control, the processing of source transactions against control budgetledgers, to see if they pass, fail, or pass with a warning.

budget control In commitment control, budget control ensures that commitments and expendituresdon’t exceed budgets. It enables you to track transactions against correspondingbudgets and terminate a document’s cycle if the defined budget conditions are not met.For example, you can prevent a purchase order from being dispatched to a vendor ifthere are insufficient funds in the related budget to support it.

budget period The interval of time (such as 12 months or 4 quarters) into which a period is dividedfor budgetary and reporting purposes. The ChartField allows maximum flexibility todefine operational accounting time periods without restriction to only one calendar.

business event In PeopleSoft Receivables, defines the processing characteristics for the ReceivableUpdate process for a draft activity.


Glossary

In PeopleSoft Sales Incentive Management, an original business transaction or activitythat may justify the creation of a PeopleSoft Enterprise Incentive Management event(a sale, for example).

business unit A corporation or a subset of a corporation that is independent with regard to one ormore operational or accounting functions.

buyer In PeopleSoft eSettlements, an organization (or business unit, as opposed to anindividual) that transacts with suppliers (vendors) within the system. A buyer createspayments for purchases that are made in the system.

catalog item In PeopleSoft Enterprise Learning Management, a specific topic that a learner canstudy and have tracked. For example, “Introduction to Microsoft Word.” A catalogitem contains general information about the topic and includes a course code,description, categorization, keywords, and delivery methods. A catalog item canhave one or more learning activities.

catalog map In PeopleSoft Catalog Management, translates values from the catalog source data tothe format of the company’s catalog.

catalog partner In PeopleSoft Catalog Management, shares responsibility with the enterprise catalogmanager for maintaining catalog content.

categorization Associates partner offerings with catalog offerings and groups them into enterprisecatalog categories.

channel In PeopleSoft MultiChannel Framework, email, chat, voice (computer telephoneintegration [CTI]), or a generic event.

ChartField A field that stores a chart of accounts, resources, and so on, depending on thePeopleSoft application. ChartField values represent individual account numbers,department codes, and so forth.

ChartField balancing You can require specific ChartFields to match up (balance) on the debit and the creditside of a transaction.

ChartField combination edit The process of editing journal lines for valid ChartField combinations based onuser-defined rules.

ChartKey One or more fields that uniquely identify each row in a table. Some tables contain onlyone field as the key, while others require a combination.

checkbook In PeopleSoft Promotions Management, enables you to view financial data (such asplanned, incurred, and actual amounts) that is related to funds and trade promotions.

Class ChartField A ChartField value that identifies a unique appropriation budget key when youcombine it with a fund, department ID, and program code, as well as a budget period.Formerly calledsub-classification.

clone In PeopleCode, to make a unique copy. In contrast, tocopymay mean making anew reference to an object, so if the underlying object is changed, both the copy andthe original change.

collection To make a set of documents available for searching in Verity, you must first createat least one collection. A collection is set of directories and files that allow searchapplication users to use the Verity search engine to quickly find and display sourcedocuments that match search criteria. A collection is a set of statistics and pointersto the source documents, stored in a proprietary format on a file server. Because acollection can only store information for a single location, PeopleSoft maintains a setof collections (one per language code) for each search index object.


Glossary

collection rule In PeopleSoft Receivables, a user-defined rule that defines actions to take for acustomer based on both the amount and the number of days past due for outstandingbalances.

compensation object In PeopleSoft Enterprise Incentive Management, a node within a compensationstructure. Compensation objects are the building blocks that make up a compensationstructure’s hierarchical representation.

compensation structure In PeopleSoft Enterprise Incentive Management, a hierarchical relationship ofcompensation objects that represents the compensation-related relationship betweenthe objects.

condition In PeopleSoft Receivables, occurs when there is a change of status for a customer’saccount, such as reaching a credit limit or exceeding a user-defined balance due.

configuration parametercatalog

Used to configure an external system with PeopleSoft. For example, a configurationparameter catalog might set up configuration and communication parameters for anexternal server.

configuration plan In PeopleSoft Enterprise Incentive Management, configuration plans hold allocationinformation for common variables (not incentive rules) and are attached to a nodewithout a participant. Configuration plans are not processed by transactions.

content reference Content references are pointers to content registered in the portal registry. These aretypically either URLs or iScripts. Content references fall into three categories: targetcontent, templates, and template pagelets.

context In PeopleCode, determines which buffer fields can be contextually referenced andwhich is the current row of data on each scroll level when a PeopleCode programis running.

In PeopleSoft Enterprise Incentive Management, a mechanism that is used todetermine the scope of a processing run. PeopleSoft Enterprise Incentive Managementuses three types of context: plan, period, and run-level.

control table Stores information that controls the processing of an application. This type ofprocessing might be consistent throughout an organization, or it might be used only byportions of the organization for more limited sharing of data.

cost profile A combination of a receipt cost method, a cost flow, and a deplete cost method. Aprofile is associated with a cost book and determines how items in that book arevalued, as well as how the material movement of the item is valued for the book.

cost row A cost transaction and amount for a set of ChartFields.

current learning In PeopleSoft Enterprise Learning Management, a self-service repository for all of alearner’s in-progress learning activities and programs.

data acquisition In PeopleSoft Enterprise Incentive Management, the process during which rawbusiness transactions are acquired from external source systems and fed into theoperational data store (ODS).

data elements Data elements, at their simplest level, define a subset of data and the rules by whichto group them.

For Workforce Analytics, data elements are rules that tell the system what measures toretrieve about your workforce groups.

dataset A data grouping that enables role-based filtering and distribution of data. You canlimit the range and quantity of data that is displayed for a user by associating datasetrules with user roles. The result of dataset rules is a set of data that is appropriatefor the user’s roles.


Glossary

delivery method In PeopleSoft Enterprise Learning Management, identifies the primary type ofdelivery method in which a particular learning activity is offered. Also providesdefault values for the learning activity, such as cost and language. This is primarilyused to help learners search the catalog for the type of delivery from which they learnbest. Because PeopleSoft Enterprise Learning Management is a blended learningsystem, it does not enforce the delivery method.

In PeopleSoft Supply Chain Management, identifies the method by which goods areshipped to their destinations (such as truck, air, rail, and so on). The delivery method isspecified when creating shipment schedules.

delivery method type In PeopleSoft Enterprise Learning Management, identifies how learning activities canbe delivered—for example, through online learning, classroom instruction, seminars,books, and so forth—in an organization. The type determines whether the deliverymethod includes scheduled components.

directory information tree In PeopleSoft Directory Interface, the representation of a directory’s hierarchicalstructure.

document sequencing A flexible method that sequentially numbers the financial transactions (for example,bills, purchase orders, invoices, and payments) in the system for statutory reportingand for tracking commercial transaction activity.

dynamic detail tree A tree that takes its detail values—dynamic details—directly from a table in thedatabase, rather than from a range of values that are entered by the user.

edit table A table in the database that has its own record definition, such as the Department table.As fields are entered into a PeopleSoft application, they can be validated against anedit table to ensure data integrity throughout the system.

effective date A method of dating information in PeopleSoft applications. You can predateinformation to add historical data to your system, or postdate information in order toenter it before it actually goes into effect. By using effective dates, you don’t deletevalues; you enter a new value with a current effective date.

EIM ledger Abbreviation forEnterprise Incentive Management ledger.In PeopleSoft EnterpriseIncentive Management, an object to handle incremental result gathering within thescope of a participant. The ledger captures a result set with all of the appropriate tracesto the data origin and to the processing steps of which it is a result.

elimination set In PeopleSoft General Ledger, a related group of intercompany accounts that isprocessed during consolidations.

entry event In PeopleSoft General Ledger, Receivables, Payables, Purchasing, and Billing, abusiness process that generates multiple debits and credits resulting from singletransactions to produce standard, supplemental accounting entries.

equitization In PeopleSoft General Ledger, a business process that enables parent companies tocalculate the net income of subsidiaries on a monthly basis and adjust that amountto increase the investment amount and equity income amount before performingconsolidations.

event A predefined point either in the Component Processor flow or in the program flow.As each point is encountered, the event activates each component, triggering anyPeopleCode program that is associated with that component and that event. Examplesof events are FieldChange, SavePreChange, and RowDelete.

In PeopleSoft Human Resources, also refers to an incident that affects benefitseligibility.

event propagation process In PeopleSoft Sales Incentive Management, a process that determines, through logic,the propagation of an original PeopleSoft Enterprise Incentive Management event andcreates a derivative (duplicate) of the original event to be processed by other objects.


Glossary

Sales Incentive Management uses this mechanism to implement splits, roll-ups, and soon. Event propagation determines who receives the credit.

exception In PeopleSoft Receivables, an item that either is a deduction or is in dispute.

exclusive pricing In PeopleSoft Order Management, a type of arbitration plan that is associated with aprice rule. Exclusive pricing is used to price sales order transactions.

fact In PeopleSoft applications, facts are numeric data values from fields from a sourcedatabase as well as an analytic application. A fact can be anything you want to measureyour business by, for example, revenue, actual, budget data, or sales numbers. Afact is stored on a fact table.

forecast item A logical entity with a unique set of descriptive demand and forecast data that is usedas the basis to forecast demand. You create forecast items for a wide range of uses, butthey ultimately represent things that you buy, sell, or use in your organization and forwhich you require a predictable usage.

fund In PeopleSoft Promotions Management, a budget that can be used to fund promotionalactivity. There are four funding methods: top down, fixed accrual, rolling accrual, andzero-based accrual.

generic process type In PeopleSoft Process Scheduler, process types are identified by a generic processtype. For example, the generic process type SQR includes all SQR process types,such as SQR process and SQR report.

group In PeopleSoft Billing and Receivables, a posting entity that comprises one or moretransactions (items, deposits, payments, transfers, matches, or write-offs).

In PeopleSoft Human Resources Management and Supply Chain Management, anyset of records that are associated under a single name or variable to run calculationsin PeopleSoft business processes. In PeopleSoft Time and Labor, for example,employees are placed in groups for time reporting purposes.

incentive object In PeopleSoft Enterprise Incentive Management, the incentive-related objects thatdefine and support the PeopleSoft Enterprise Incentive Management calculationprocess and results, such as plan templates, plans, results data, user interaction objects,and so on.

incentive rule In PeopleSoft Sales Incentive Management, the commands that act on transactions andturn them into compensation. A rule is one part in the process of turning a transactioninto compensation.

incur In PeopleSoft Promotions Management, to become liable for a promotional payment.In other words, you owe that amount to a customer for promotional activities.

item In PeopleSoft Inventory, a tangible commodity that is stored in a business unit(shipped from a warehouse).

In PeopleSoft Demand Planning, Inventory Policy Planning, and Supply Planning, anoninventory item that is designated as being used for planning purposes only. It canrepresent a family or group of inventory items. It can have a planning bill of material(BOM) or planning routing, and it can exist as a component on a planning BOM. Aplanning item cannot be specified on a production or engineering BOM or routing,and it cannot be used as a component in a production. The quantity on hand willnever be maintained.

In PeopleSoft Receivables, an individual receivable. An item can be an invoice, acredit memo, a debit memo, a write-off, or an adjustment.

KPI An abbreviation forkey performance indicator.A high-level measurement of how wellan organization is doing in achieving critical success factors. This defines the datavalue or calculation upon which an assessment is determined.


Glossary

LDIF file Abbreviation forLightweight Directory Access Protocol (LDAP) Data InterchangeFormat file.Contains discrepancies between PeopleSoft data and directory data.

learner group In PeopleSoft Enterprise Learning Management, a group of learners who are linkedto the same learning environment. Members of the learner group can share the sameattributes, such as the same department or job code. Learner groups are used to controlaccess to and enrollment in learning activities and programs. They are also used toperform group enrollments and mass enrollments in the back office.

learning components In PeopleSoft Enterprise Learning Management, the foundational building blocksof learning activities. PeopleSoft Enterprise Learning Management supports sixbasic types of learning components: web-based, session, webcast, test, survey, andassignment. One or more of these learning component types compose a singlelearning activity.

learning environment In PeopleSoft Enterprise Learning Management, identifies a set of categories andcatalog items that can be made available to learner groups. Also defines the defaultvalues that are assigned to the learning activities and programs that are created within aparticular learning environment. Learning environments provide a way to partition thecatalog so that learners see only those items that are relevant to them.

learning history In PeopleSoft Enterprise Learning Management, a self-service repository for all of alearner’s completed learning activities and programs.

ledger mapping You use ledger mapping to relate expense data from general ledger accounts toresource objects. Multiple ledger line items can be mapped to one or more resourceIDs. You can also use ledger mapping to map dollar amounts (referred to asrates)to business units. You can map the amounts in two different ways: an actual amountthat represents actual costs of the accounting period, or a budgeted amount that can beused to calculate the capacity rates as well as budgeted model results. In PeopleSoftEnterprise Warehouse, you can map general ledger accounts to the EW Ledger table.

library section In PeopleSoft Enterprise Incentive Management, a section that is defined in a plan (ortemplate) and that is available for other plans to share. Changes to a library section arereflected in all plans that use it.

linked section In PeopleSoft Enterprise Incentive Management, a section that is defined in a plantemplate but appears in a plan. Changes to linked sections propagate to plans usingthat section.

linked variable In PeopleSoft Enterprise Incentive Management, a variable that is defined andmaintained in a plan template and that also appears in a plan. Changes to linkedvariables propagate to plans using that variable.

load In PeopleSoft Inventory, identifies a group of goods that are shipped together. Loadmanagement is a feature of PeopleSoft Inventory that is used to track the weight, thevolume, and the destination of a shipment.

local functionality In PeopleSoft HRMS, the set of information that is available for a specific country.You can access this information when you click the appropriate country flag in theglobal window, or when you access it by a local country menu.

location Locations enable you to indicate the different types of addresses—for a company, forexample, one address to receive bills, another for shipping, a third for postal deliveries,and a separate street address. Each address has a different location number. Theprimary location—indicated by a1—is the address you use most often and may bedifferent from the main address.

logistical task In PeopleSoft Services Procurement, an administrative task that is related to hiringa service provider. Logistical tasks are linked to the service type on the work orderso that different types of services can have different logistical tasks. Logistical tasksinclude both preapproval tasks (such as assigning a new badge or ordering a new


Glossary

laptop) and postapproval tasks (such as scheduling orientation or setting up the serviceprovider email). The logistical tasks can be mandatory or optional. Mandatorypreapproval tasks must be completed before the work order is approved. Mandatorypostapproval tasks, on the other hand, must be completed before a work order isreleased to a service provider.

market template In PeopleSoft Enterprise Incentive Management, additional functionality that isspecific to a given market or industry and is built on top of a product category.

match group In PeopleSoft Receivables, a group of receivables items and matching offset items.The system creates match groups by using user-defined matching criteria for selectedfield values.

MCF server Abbreviation forPeopleSoft MultiChannel Framework server.Comprises theuniversal queue server and the MCF log server. Both processes are started whenMCFServersis selected in an application server domain configuration.

merchandising activity In PeopleSoft Promotions Management, a specific discount type that is associated witha trade promotion (such as off-invoice, billback or rebate, or lump-sum payment) thatdefines the performance that is required to receive the discount. In the industry, youmay know this as an offer, a discount, a merchandising event, an event, or a tactic.

meta-SQL Meta-SQL constructs expand into platform-specific Structured Query Language(SQL) substrings. They are used in functions that pass SQL strings, such as in SQLobjects, the SQLExec function, and PeopleSoft Application Engine programs.

metastring Metastrings are special expressions included in SQL string literals. The metastrings,prefixed with a percent (%) symbol, are included directly in the string literals. Theyexpand at run time into an appropriate substring for the current database platform.

multibook In PeopleSoft General Ledger, multiple ledgers having multiple-base currencies thatare defined for a business unit, with the option to post a single transaction to all basecurrencies (all ledgers) or to only one of those base currencies (ledgers).

multicurrency The ability to process transactions in a currency other than the business unit’s basecurrency.

national allowance In PeopleSoft Promotions Management, a promotion at the corporate level that isfunded by nondiscretionary dollars. In the industry, you may know this as a nationalpromotion, a corporate promotion, or a corporate discount.

node-oriented tree A tree that is based on a detail structure, but the detail values are not used.

pagelet Each block of content on the home page is called a pagelet. These pagelets displaysummary information within a small rectangular area on the page. The pagelet provideusers with a snapshot of their most relevant PeopleSoft and non-PeopleSoft content.

participant In PeopleSoft Enterprise Incentive Management, participants are recipients of theincentive compensation calculation process.

participant object Each participant object may be related to one or more compensation objects.

See alsocompensation object.

partner A company that supplies products or services that are resold or purchased by theenterprise.

pay cycle In PeopleSoft Payables, a set of rules that define the criteria by which it should selectscheduled payments for payment creation.

pending item In PeopleSoft Receivables, an individual receivable (such as an invoice, a creditmemo, or a write-off) that has been entered in or created by the system, but hasn’tbeen posted.


Glossary

PeopleCode PeopleCode is a proprietary language, executed by the PeopleSoft applicationprocessor. PeopleCode generates results based upon existing data or user actions. Byusing business interlink objects, external services are available to all PeopleSoftapplications wherever PeopleCode can be executed.

PeopleCode event An action that a user takes upon an object, usually a record field, that is referencedwithin a PeopleSoft page.

PeopleSoft InternetArchitecture

The fundamental architecture on which PeopleSoft 8 applications are constructed,consisting of a relational database management system (RDBMS), an applicationserver, a web server, and a browser.

performance measurement In PeopleSoft Enterprise Incentive Management, a variable used to store data (similarto an aggregator, but without a predefined formula) within the scope of an incentiveplan. Performance measures are associated with a plan calendar, territory, andparticipant. Performance measurements are used for quota calculation and reporting.

period context In PeopleSoft Enterprise Incentive Management, because a participant typicallyuses the same compensation plan for multiple periods, the period context associatesa plan context with a specific calendar period and fiscal year. The period contextreferences the associated plan context, thus forming a chain. Each plan context has acorresponding set of period contexts.

plan In PeopleSoft Sales Incentive Management, a collection of allocation rules, variables,steps, sections, and incentive rules that instruct the PeopleSoft Enterprise IncentiveManagement engine in how to process transactions.

plan context In PeopleSoft Enterprise Incentive Management, correlates a participant withthe compensation plan and node to which the participant is assigned, enablingthe PeopleSoft Enterprise Incentive Management system to find anything that isassociated with the node and that is required to perform compensation processing.Each participant, node, and plan combination represents a unique plan context—ifthree participants are on a compensation structure, each has a different plan context.Configuration plans are identified by plan contexts and are associated with theparticipants that refer to them.

plan template In PeopleSoft Enterprise Incentive Management, the base from which a plan is created.A plan template contains common sections and variables that are inherited by all plansthat are created from the template. A template may contain steps and sections thatare not visible in the plan definition.

planned learning In PeopleSoft Enterprise Learning Management, a self-service repository for all ofa learner’s planned learning activities and programs.

planning instance In PeopleSoft Supply Planning, a set of data (business units, items, supplies, anddemands) constituting the inputs and outputs of a supply plan.

portal registry In PeopleSoft applications, the portal registry is a tree-like structure in which contentreferences are organized, classified, and registered. It is a central repository thatdefines both the structure and content of a portal through a hierarchical, tree-likestructure of folders useful for organizing and securing content references.

price list In PeopleSoft Enterprise Pricer, enables you to select products and conditions forwhich the price list applies to a transaction. During a transaction, the system eitherdetermines the product price based on the predefined search hierarchy for thetransaction or uses the product’s lowest price on any associated, active price lists. Thisprice is used as the basis for any further discounts and surcharges.

price rule In PeopleSoft Enterprise Pricer, defines the conditions that must be met foradjustments to be applied to the base price. Multiple rules can apply when conditionsof each rule are met.


Glossary

price rule condition In PeopleSoft Enterprise Pricer, selects the price-by fields, the values for the price-byfields, and the operator that determines how the price-by fields are related to thetransaction.

price rule key In PeopleSoft Enterprise Pricer, defines the fields that are available to define price ruleconditions (which are used to match a transaction) on the price rule.

process category In PeopleSoft Process Scheduler, processes that are grouped for server load balancingand prioritization.

process group In PeopleSoft Financials, a group of application processes (performed in a definedorder) that users can initiate in real time, directly from a transaction entry page.

process definition Process definitions define each run request.

process instance A unique number that identifies each process request. This value is automaticallyincremented and assigned to each requested process when the process is submitted torun.

process job You can link process definitions into a job request and process each request seriallyor in parallel. You can also initiate subsequent processes based on the return codefrom each prior request.

process request A single run request, such as a Structured Query Report (SQR), a COBOL orApplication Engine program, or a Crystal report that you run through PeopleSoftProcess Scheduler.

process run control A PeopleTools variable used to retain PeopleSoft Process Scheduler values neededat runtime for all requests that reference a run control ID. Do not confuse these withapplication run controls, which may be defined with the same run control ID, but onlycontain information specific to a given application process request.

product category In PeopleSoft Enterprise Incentive Management, indicates an application in theEnterprise Incentive Management suite of products. Each transaction in the PeopleSoftEnterprise Incentive Management system is associated with a product category.

programs In PeopleSoft Enterprise Learning Management, a high-level grouping that guides thelearner along a specific learning path through sections of catalog items. PeopleSoftEnterprise Learning Systems provides two types of programs—curricula andcertifications.

progress log In PeopleSoft Services Procurement, tracks deliverable-based projects. This is similarto the time sheet in function and process. The service provider contact uses theprogress log to record and submit progress on deliverables. The progress can be loggedby the activity that is performed, by the percentage of work that is completed, or by thecompletion of milestone activities that are defined for the project.

project transaction In PeopleSoft Project Costing, an individual transaction line that represents a cost,time, budget, or other transaction row.

promotion In PeopleSoft Promotions Management, a trade promotion, which is typically fundedfrom trade dollars and used by consumer products manufacturers to increase salesvolume.

publishing In PeopleSoft Enterprise Incentive Management, a stage in processing that makesincentive-related results available to participants.

record group A set of logically and functionally related control tables and views. Record groupshelp enable TableSet sharing, which eliminates redundant data entry. Record groupsensure that TableSet sharing is applied consistently across all related tables and views.

record input VAT flag Abbreviation forrecord input value-added tax flag.Within PeopleSoft Purchasing,Payables, and General Ledger, this flag indicates that you are recording input VAT


Glossary

on the transaction. This flag, in conjunction with the record output VAT flag, is usedto determine the accounting entries created for a transaction and to determine how atransaction is reported on the VAT return. For all cases within Purchasing and Payableswhere VAT information is tracked on a transaction, this flag is set to Yes. This flagis not used in PeopleSoft Order Management, Billing, or Receivables, where it isassumed that you are always recording only output VAT, or in PeopleSoft Expenses,where it is assumed that you are always recording only input VAT.

record output VAT flag Abbreviation forrecord output value-added tax flag.

Seerecord input VAT flag.

reference data In PeopleSoft Sales Incentive Management, system objects that represent the salesorganization, such as territories, participants, products, customers, channels, and so on.

reference object In PeopleSoft Enterprise Incentive Management, this dimension-type object furtherdefines the business. Reference objects can have their own hierarchy (for example,product tree, customer tree, industry tree, and geography tree).

reference transaction In commitment control, a reference transaction is a source transaction that isreferenced by a higher-level (and usually later) source transaction, in order toautomatically reverse all or part of the referenced transaction’s budget-checkedamount. This avoids duplicate postings during the sequential entry of the transaction atdifferent commitment levels. For example, the amount of an encumbrance transaction(such as a purchase order) will, when checked and recorded against a budget, causethe system to concurrently reference and relieve all or part of the amount of acorresponding pre-encumbrance transaction, such as a purchase requisition.

regional sourcing In PeopleSoft Purchasing, provides the infrastructure to maintain, display, and selectan appropriate vendor and vendor pricing structure that is based on a regional sourcingmodel where the multiple ship to locations are grouped. Sourcing may occur at alevel higher than the ship to location.

relationship object In PeopleSoft Enterprise Incentive Management, these objects further define acompensation structure to resolve transactions by establishing associations betweencompensation objects and business objects.

remote data source data Data that is extracted from a separate database and migrated into the local database.

REN server Abbreviation forreal-time event notification serverin PeopleSoft MultiChannelFramework.

requester In PeopleSoft eSettlements, an individual who requests goods or services and whoseID appears on the various procurement pages that reference purchase orders.

role Describes how people fit into PeopleSoft Workflow. A role is a class of users whoperform the same type of work, such as clerks or managers. Your business rulestypically specify what user role needs to do an activity.

role user A PeopleSoft Workflow user. A person’s role user ID serves much the same purpose asa user ID does in other parts of the system. PeopleSoft Workflow uses role user IDsto determine how to route worklist items to users (through an email address, forexample) and to track the roles that users play in the workflow. Role users do not needPeopleSoft user IDs.

roll up In a tree, to roll up is to total sums based on the information hierarchy.

run control A run control is a type of online page that is used to begin a process, such as thebatch processing of a payroll run. Run control pages generally start a program thatmanipulates data.

run control ID A unique ID to associate each user with his or her own run control table entries.


Glossary

run-level context In PeopleSoft Enterprise Incentive Management, associates a particular run (and batchID) with a period context and plan context. Every plan context that participates in a runhas a separate run-level context. Because a run cannot span periods, only one run-levelcontext is associated with each plan context.

search query You use this set of objects to pass a query string and operators to the search engine.The search index returns a set of matching results with keys to the source documents.

section In PeopleSoft Enterprise Incentive Management, a collection of incentive rules thatoperate on transactions of a specific type. Sections enable plans to be segmented toprocess logical events in different sections.

security event In commitment control, security events trigger security authorization checking, suchas budget entries, transfers, and adjustments; exception overrides and notifications;and inquiries.

serial genealogy In PeopleSoft Manufacturing, the ability to track the composition of a specific,serial-controlled item.

serial in production In PeopleSoft Manufacturing, enables the tracing of serial information formanufactured items. This is maintained in the Item Master record.

session In PeopleSoft Enterprise Learning Management, a single meeting day of an activity(that is, the period of time between start and finish times within a day). The sessionstores the specific date, location, meeting time, and instructor. Sessions are used forscheduled training.

session template In PeopleSoft Enterprise Learning Management, enables you to set up commonactivity characteristics that may be reused while scheduling a PeopleSoft EnterpriseLearning Management activity—characteristics such as days of the week, start andend times, facility and room assignments, instructors, and equipment. A sessionpattern template can be attached to an activity that is being scheduled. Attaching atemplate to an activity causes all of the default template information to populatethe activity session pattern.

setup relationship In PeopleSoft Enterprise Incentive Management, a relationship object type thatassociates a configuration plan with any structure node.

share driver expression In PeopleSoft Business Planning, a named planning method similar to a driverexpression, but which you can set up globally for shared use within a single planningapplication or to be shared between multiple planning applications through PeopleSoftEnterprise Warehouse.

single signon With single signon, users can, after being authenticated by a PeopleSoft applicationserver, access a second PeopleSoft application server without entering a user ID orpassword.

source transaction In commitment control, any transaction generated in a PeopleSoft or third-partyapplication that is integrated with commitment control and which can be checkedagainst commitment control budgets. For example, a pre-encumbrance, encumbrance,expenditure, recognized revenue, or collected revenue transaction.

SpeedChart A user-defined shorthand key that designates several ChartKeys to be used for voucherentry. Percentages can optionally be related to each ChartKey in a SpeedChartdefinition.

SpeedType A code representing a combination of ChartField values. SpeedTypes simplify theentry of ChartFields commonly used together.

staging A method of consolidating selected partner offerings with the offerings from theenterprise’s other partners.


Glossary

statutory account Account required by a regulatory authority for recording and reporting financialresults. In PeopleSoft, this is equivalent to the Alternate Account (ALTACCT)ChartField.

step In PeopleSoft Sales Incentive Management, a collection of sections in a plan. Eachstep corresponds to a step in the job run.

storage level In PeopleSoft Inventory, identifies the level of a material storage location. Materialstorage locations are made up of a business unit, a storage area, and a storage level.You can set up to four storage levels.

subcustomer qualifier A value that groups customers into a division for which you can generate detailedhistory, aging, events, and profiles.

Summary ChartField You use summary ChartFields to create summary ledgers that roll up detail amountsbased on specific detail values or on selected tree nodes. When detail values aresummarized using tree nodes, summary ChartFields must be used in the summaryledger data record to accommodate the maximum length of a node name (20characters).

summary ledger An accounting feature used primarily in allocations, inquiries, and PS/nVisionreporting to store combined account balances from detail ledgers. Summary ledgersincrease speed and efficiency of reporting by eliminating the need to summarizedetail ledger balances each time a report is requested. Instead, detail balances aresummarized in a background process according to user-specified criteria and stored onsummary ledgers. The summary ledgers are then accessed directly for reporting.

summary time period In PeopleSoft Business Planning, any time period (other than a base time period) that isan aggregate of other time periods, including other summary time periods and basetime periods, such as quarter and year total.

summary tree A tree used to roll up accounts for each type of report in summary ledgers. Summarytrees enable you to define trees on trees. In a summary tree, the detail values are reallynodes on a detail tree or another summary tree (known as thebasistree). A summarytree structure specifies the details on which the summary trees are to be built.

syndicate To distribute a production version of the enterprise catalog to partners.

system function In PeopleSoft Receivables, an activity that defines how the system generatesaccounting entries for the general ledger.

TableSet A means of sharing similar sets of values in control tables, where the actual data valuesare different but the structure of the tables is the same.

TableSet sharing Shared data that is stored in many tables that are based on the same TableSets. Tablesthat use TableSet sharing contain the SETID field as an additional key or uniqueidentifier.

target currency The value of the entry currency or currencies converted to a single currency for budgetviewing and inquiry purposes.

template A template is HTML code associated with a web page. It defines the layout ofthe page and also where to get HTML for each part of the page. In PeopleSoft, youuse templates to build a page by combining HTML from a number of sources. Fora PeopleSoft portal, all templates must be registered in the portal registry, and eachcontent reference must be assigned a template.

territory In PeopleSoft Sales Incentive Management, hierarchical relationships of businessobjects, including regions, products, customers, industries, and participants.

TimeSpan A relative period, such as year-to-date or current period, that can be used in variousPeopleSoft General Ledger functions and reports when a rolling time frame, rather


Glossary

than a specific date, is required. TimeSpans can also be used with flexible formulas inPeopleSoft Projects.

trace usage In PeopleSoft Manufacturing, enables the control of which components will be tracedduring the manufacturing process. Serial- and lot-controlled components can betraced. This is maintained in the Item Master record.

transaction allocation In PeopleSoft Enterprise Incentive Management, the process of identifying the ownerof a transaction. When a raw transaction from a batch is allocated to a plan context,the transaction is duplicated in the PeopleSoft Enterprise Incentive Managementtransaction tables.

transaction state In PeopleSoft Enterprise Incentive Management, a value assigned by an incentiverule to a transaction. Transaction states enable sections to process only transactionsthat are at a specific stage in system processing. After being successfully processed,transactions may be promoted to the next transaction state and “picked up” by adifferent section for further processing.

Translate table A system edit table that stores codes and translate values for the miscellaneous fields inthe database that do not warrant individual edit tables of their own.

tree The graphical hierarchy in PeopleSoft systems that displays the relationship betweenall accounting units (for example, corporate divisions, projects, reporting groups,account numbers) and determines roll-up hierarchies.

unclaimed transaction In PeopleSoft Enterprise Incentive Management, a transaction that is not claimedby a node or participant after the allocation process has completed, usually due tomissing or incomplete data. Unclaimed transactions may be manually assigned to theappropriate node or participant by a compensation administrator.

universal navigation header Every PeopleSoft portal includes the universal navigation header, intended to appear atthe top of every page as long as the user is signed on to the portal. In addition toproviding access to the standard navigation buttons (like Home, Favorites, and signoff)the universal navigation header can also display a welcome message for each user.

user interaction object In PeopleSoft Sales Incentive Management, used to define the reporting componentsand reports that a participant can access in his or her context. All Sales IncentiveManagement user interface objects and reports are registered as user interactionobjects. User interaction objects can be linked to a compensation structure nodethrough a compensation relationship object (individually or as groups).

variable In PeopleSoft Sales Incentive Management, the intermediate results of calculations.Variables hold the calculation results and are then inputs to other calculations.Variables can be plan variables that persist beyond the run of an engine or localvariables that exist only during the processing of a section.

VAT exception Abbreviation forvalue-added tax exception.A temporary or permanent exemptionfrom paying VAT that is granted to an organization. This terms refers to both VATexoneration and VAT suspension.

VAT exempt Abbreviation forvalue-added tax exempt.Describes goods and services that are notsubject to VAT. Organizations that supply exempt goods or services are unable torecover the related input VAT. This is also referred to as exempt without recovery.

VAT exoneration Abbreviation forvalue-added tax exoneration.An organization that has been granted apermanent exemption from paying VAT due to the nature of that organization.

VAT suspension Abbreviation forvalue-added tax suspension.An organization that has been granted atemporary exemption from paying VAT.

warehouse A PeopleSoft data warehouse that consists of predefined ETL maps, data warehousetools, and DataMart definitions.


Glossary

work order In PeopleSoft Services Procurement, enables an enterprise to create resource-basedand deliverable-based transactions that specify the basic terms and conditions forhiring a specific service provider. When a service provider is hired, the serviceprovider logs time or progress against the work order.

worksheet A way of presenting data through a PeopleSoft Business Analysis Modeler interfacethat enables users to do in-depth analysis using pivoting tables, charts, notes, andhistory information.

worklist The automated to-do list that PeopleSoft Workflow creates. From the worklist, youcan directly access the pages you need to perform the next action, and then return tothe worklist for another item.

XML schema An XML definition that standardizes the representation of application messages,component interfaces, or business interlinks.

yield by operation In PeopleSoft Manufacturing, the ability to plan the loss of a manufactured item on anoperation-by-operation basis.

zero-rated VAT Abbreviation forzero-rated value-added tax.A VAT transaction with a VAT code thathas a tax percent of zero. Used to track taxable VAT activity where no actual VATamount is charged. Organizations that supply zero-rated goods and services can stillrecover the related input VAT. This is also referred to as exempt with recovery.


Glossary


Index

Numerics/Symbols1219 report, printing 577

AAccount component (GL_ACCOUNT) 243, 500, 526

ACCOUNT_CF, component interface 6,243, 500, 526

accounting entriescontributor relations 418generic 417–418imported 417payroll 418student financial 418

accounting lines inquiry, navigationpages 418

activating integrations 68actuals and recognized, selectingCommitment Control amount type 455

actuals, recognize, and collect, selectingCommitment Control amount type 456

ADBdefining process requestparameters 273

incremental calculation method 26incremental calculations 260management and regulatorybalances 265

posting and calculation activities 272preparing for ADB calculations 267processing 272processing Period 998 adjustments 264producing reports 275reporting date 265reversal 118understanding adjustments 263using ChartField values in balances 270

ADB calculation 255ad hoc 262defining methods 259incremental and ad hoc method 259

ADB Calculation process, optimizing 102ADB Calculation report, GLC5501 603ADB ChartFields page 270

ADB Definition component(ADB_DEFN) 267

ADB Definition report 276GLS5500 608

ADB Process Request page 273ADB_DEFN component 267additional documentation xxviALLOC_COPY_LEDGERcomponent 432

ALLOC_GROUP_BD component 432Allocation Calculation Log report,GLS6002 608

Allocation Group report, GLC6001 603Allocation process 48

standard budgets 425allocations, entry events 483ALTACCT_CF, component interface 4Alternate Account Edit process 49Amount Suspense ChartFields page 31,34

amount type, Commitment Controlactuals and recognized 455actuals, recognize, collect 456collected revenue 456encumbrance 455planned 456pre-encumbrance 456

application fundamentals xxvapplication integration 63Application Messaging for general ledgerdatabases 359

application pages, initiating processesfrom 43, 45

Approval Options page - General LedgerDefinition 35

approval options, specifying 35Approval page - Journal Entry 142archiving ledgers and journals 439

archive date 440archiving and restoring journals 445archiving to a file 439archiving to a table 439calendars 440journals, pages used 445ledgers 441–442


Index

pages used to archive and restoreledgers 442

restoring archived journals 446restoring archived ledger data 443retention days 440

archiving ledgers and journals, viewingarchive journal log 441archive ledger log 444

attributescross-references 545FACTS II, account 544FACTS II, fund code, account 542setting up FACTS II 533

Audit Elimination Sets Audit report,GLS2005 606

Average Daily Balance Calculationprocess 49

Average Daily Balances (ADB)incremental calculation methods 29prerequisites 255

Bbackground editing, initiating 201background processes

application pages, initiating from 43,45

concurrency 48understanding 43

Balance Suspense ChartFields page 31,33

base amount field 394base currency value, preparing torevalue 278

baseline, establishing measuringmethod 87

budgetallocation process 425copy group 436copy process, initiating 437copy, using allocations 437copying 432details 461importing from spreadsheets 437journals, posting 438spreading, repeating, increasingpercentages 423

using override 461budget ChartFields, viewing 461budget checking

Commitment Control bypassing 457

Commitment Control errors 460errors, journal entries 458overrides 460

Budget Copy Calculation Log report,GLS6003 609

Budget Copy Definition component(ALLOC_COPY_LEDGER) 432

Budget Copy Group component(ALLOC_GROUP_BD) 432

budget detailmaintain navigation pages 427maintaining 426

budget exceptionsdrilling down 462journal lines 462limiting number of journal lines 462

budget, adjustingdata by period 429data by year 428

BUDGET_REF_CF, componentinterface 4

BUDGET_SCENARIO, componentinterface 4

budgets, standard 421creating and maintaining 422prerequisites 421

Build Ledger Cubes Request page 494BUS_UNIT_TBL_GL component 27,30, 34–35, 243

business processgeneral ledger 1, 20general ledger workflow maps 465

business unitsapproval options 25changing unpost date 194currency options 25defining 25GL definition page 28journal options 25specifying ledgers for 348VAT defaults 25

bypass budget checking 457

Ccalculating average balances 255

ad hoc calculation method 262incremental and ad hoc method 259incremental calculation method 260

CF_ATTRIBUTES component 500CF_MAPPING_SET component 338


Index

CF_VALUE_MAPPING component 338Change ChartField Values page 215ChartField Attributes component(CF_ATTRIBUTES) 500, 526

ChartField Combination Editingprocess 51

ChartField Mapping Set component(CF_MAPPING_SET) 338

ChartField Value Mapping component(CF_VALUE_MAPPING) 338

ChartField Value Sets, closing interim andyear end 367

ChartField values page 332CHARTFIELD1, component interface 5CHARTFIELD2, component interface 5CHARTFIELD3, component interface 5ChartFields

consolidating 315–316determining for consolidations 315FACTS I attributes 504FACTS II data, rolling up 551standard budgets 427using affiliate 312

Chartfields page - Translate WithinLedger 296

ChartFields, miscellaneousFACTS II 544

ChartFields, specifying miscellaneousFACTS I 505

charts of accounts, mapping forconsolidations 338

CLASS_CF, component interface 5CLOSE_DEFN component 376closed item 224closing

Close Request Process page 386managing interim and year end 365open item balances 227running process 386running request 371year end 372

Closing Options page 377Closing process 51closing retained earnings

multiple accounts 367single account 366

closing rulesdefining 370, 376generating report 390Journal Options page 383

report (GLS1002 SQR) 390Closing Rules component(CLOSE_DEFN) 376

Closing Rules report, GLS1002 604Closing Trial Balance report,GLS1003 390, 604

closing, interim 369comparing with year end 365procedure 370

closing, retained earnings, single vs.multiple 366

COBOL SQL batch processes, usingnon-shared tables 79

Cognos PowerPlay 491collected revenue, selecting CommitmentControl amount type 456

Combination Group report, GLC4003 603Combination Rule report, GLS4002 607combination rules 105comments, submitting xxixcommitment control

creating journal entries in GL 453journal entries 451journal entries, navigation pages 452selecting amount types 454status codes 460

Commitment Control 457budget adjustment journals, entryevents 451

budget checking errors 460entering and processing journallines 457

journal entries 450journal entries, entry events 451

See Alsoentry eventsusing entry events in journal entries 458using for General Ledger journalentries 449

commitment control and generalledger 449

Commitment Control Budget Closingprocess 52

commitment control budget journalsimporting flat files import 77

Commitment Control Budget Postprocess 52

Commitment Control Budget Processorprocess 52

common elements xxixGeneral Ledger PeopleBook xxxii


Index

compareamounts between ledgers 415data across ledgers 413data by ledger periods 409

component interfaceACCOUNT_CF 6ALTACCT_CF 4BUDGET_REF_CF 4BUDGET_SCENARIO 4CHARTFIELD1 5CHARTFIELD2 5CHARTFIELD3 5CLASS_CF 5DEPT_CF 5FUND_CF 5IU_INTER_TMPLT 6IU_INTRA_TMPLT 6IU_PAIRS_MAINT 6OPER_UNIT_CF 7OPR_DEFAULT_FIN 7PRODUCT_CF 7PROGRAM_CF 7PROJECT_CF 7SECURITY_BU_CLS 7SECURITY_BU_OPR 8SECURITY_CF_PAGELET 6SECURITY_LEDGER_CLS 8SECURITY_LEDGER_OPR 8SECURITY_NVISION_LEDGER 6STATISTICS_CODE 8TAX_AUTHORITY_VAT 8TAX_BU_CODE_VAT 8TAX_CODE_VAT 9VAT_ENTITY_ID 9

component interface tablegeneral ledger 4, 23

CONSOL_DEFINITION component 328CONSOL_OWNERSHIPcomponent 325

Consolidated Publications Incorporated(CPI) xxvi

Consolidation Dashboard page 336Consolidation Definition component,Journal Options page 329

Consolidation Ledger Sets component(LEDGER_SET) 320

Consolidation Log page 335Consolidation Out of Balance report,GLS2003 606

Consolidation Process Monitor page 56

Consolidation Set component(CONSOL_DEFINITION) 328

Consolidation Set Report page 358Consolidation Set report, GLS9002 606consolidations

across summary ledgers 337determining ChartFields 315inter/intraunit 235mapping dissimilar charts ofaccount 338

minority interest sets on summaryledgers 338

performing 309, 332processing components 314setting up options and controls 328transferring ledgers 77trees and, viewing 335understanding 309

Consolidations process 56consolidations, defining

business unit trees 348ChartField value sets 332consolidation sets on summaryledgers 338

elimination sets for summaryledgers 337

elimination units 348scopes with trees 317trees 317

consolidations, specifyingjournal options 329ledgers 320summary ledgers 337

contact information xxixContact Information component(F2_CONTACT) 526

contact information, FACTS II 531copy

budget definition, Pool page 433budget definition, Target page 435budget group 436budgets 432budgets, navigation pages 433standard budgets 425

Copy Journal component, Journal CopyReq 154

copy journals, entry event 484correcting journal entries — no entry eventerrors 488

correction journals 219


Index

country-specific documentation xxviiicross-references xxviii

attributes 545treasury symbol, FACTS II 549

cubesanalyzing cube data 496building 494defining 493planning 492preparing trees and queries 492understanding 491

cumulative balance 393CURR_GROUP component 298Currency Group component(CURR_GROUP) 298

Currency Options page - General LedgerDefinition 34

currency options, business unitdefaults 34

current date, and journal processing 26,31

Customer Connection web site xxvi

Ddebit/credit, separate entries using entryevents 483

deferred processing xxxidefine

operational structure 25Definition page - General LedgerDefinition 28

DEPT_CF, component interface 5detail inquiry options 408detail standard budgets 426detail values, adding to Consolidationstree 318

DETAIL_LEDGER_GROUcomponent 143

documentationcountry-specific xxviiiprinted xxvirelated xxviupdates xxvi

drilling downentry event accounting 489subsystem accounting entries 404

Eedit requests, checking status 203

Edit Suspense ChartFields page 31, 33EIP, Seeenterprise integration points (EIP)elimination entries, creating 345Elimination Set Definition report,GLS2000 605

Elimination Set page 323Elimination Sets component(ELIMINATION_SET) 322–323

Elimination Sets page 357elimination sets, defining 322elimination units

adding 319assigning ledgers to 320setting up 319

ELIMINATION_SET component 322encumbrance, selecting CommitmentControl amount type 455

enterprise integration points (EIP)general ledger 63

entry event accountingbudget 419GL adjustment 420

entry event journals, GLJE 486entry event, correcting

suspense journals 489entry events 484

allocations 483budget adjustment journal,GLJEADJ 458

correcting errors 488drilling down in general ledger 489Flat File journal imports 484general ledger 477GLJE entry event process 458interunit journal entries 481journal entries, creating andprocessing 484

multibook ledgers 481separate debit/credit 483spreadsheet journals, importing 484standard journal entries (SJE) 483understanding 477

environmental variable 65EPM Budgeting 8.3, general ledgerintegrating 75

equitizationperforming 354reviewing components 347specifying sources 349specifying targets 350


Index

understanding 344Equitization Calc page 358Equitization Calculation Log report,GLS2008 607

Equitization Group component(EQUITIZATION_GROUP) 352

Equitization Log page 357Equitization process 56Equitization reports, producing forconsolidations 357

Equitization Rules component(EQUITIZATION_RULE) 349Minority Interest page 352Source page 349Subsidiary Offset page 351Target page 350

Equitization Rules page 358Equitization Rules report, GLS2006 606Equitization rules, defining 349EQUITIZATION_GROUPcomponent 352

EQUITIZATION_RULE component 349equitized sources, offsetting 346errors

correcting journal entry budgetchecking 460

entry event 488Errors page - Journal Entry 141events, journal entry approvalworkflow 474

FF2_ATTRIB_XREF component 526F2_CONTACT component 526F2_ELEMENT_CF component 500, 526F2_TSYM_XREF component 526FACTS I

ChartField attributes 504ChartFields, miscellaneous 505generating flat file 522MAF 523navigation pages 504, 507overview 501prerequisites 503processing, overview 503tableset control 520transaction partner/acct. 516tree group 518

FACTS I Trial Balance 611FACTS I, setting up 500–501

flat file 525overview 527

FACTS I, treeaccount 510–511accounts requiring attributes 517budget subfunction/account 514bureau 508custodial/acct 513exchange/acct 512fund group 509overview 501tran partner 515

FACTS IIaccumulating data 565contact information 531creating flat file 569flat file pages 563generating flat file 562Ledger with Attributes report 570MAF data, loading 546MAF data, reviewing 547miscellaneous ChartFields, adding 544pages used to set up 529preparer file 532prerequisites 528processing, overview 528reporting overview 527review setup 564reviewing validated data 566treasury symbol cross-reference 549tree group 560validating data 569

FACTS II Attribute Cross Referencecomponent (F2_ATTRIB_XREF) 526

FACTS II, attributesaccount, linking 544ChartField table 534cross-references 545fund code, account, linking 542setting up 533

FACTS II, setting up 526attributes 533trees, overview 527

FACTS II, treesaccount roll-up 552accounts requiring attributes 554category B 553cohort year 553creating 549navigation pages 550


Index

setting up overview 527FACTS Tree Group component(FACTS_TREE_GRP) 506, 549

FACTS_TREE_GRP component 506,549

FED_RC02_ACCTS tree, FUND_STATUSreport 582

Federal Transaction Register,GLS8501 611

Federal Trial Balance report,GLS8500 611

file import processes, general ledger 65FIN1001, Message Log report 601FIN2001, Journal Entry Detail report 602FIN2005, Journal Entry Detail Report withAttributes 602

FIN5001 report, Reconciliation by SystemSource 602

FIN5005 report, Reconciliation byChartField 603

financial information, reviewing 393flat file

FACTS I 522FACTS II 562, 569importing journals 76journal import 170

Flat File Journal Import process 57Flat File Ledger Import process 57FS_ALLC process 48FS_CEDT_PROC process 51FS_JGEN process 59FSPCCURR process 61FSPKBDP3 process 52FSPQPOST process 52FSPYCLOS process 52full sync data, publishing 73functional usage, processes 45Fund Balance Reconciliation

accounts, defining 579entry events, defining 580navigation pages 579report, generating 581U.S. Treasury data, importing 580

Fund Balance Reconciliation Report,overview 578

Fund Balance Reconciliation,GLS9500 612

Fund Code component (FUND_DEFINITION) 500, 526

FUND_BALANCE report

defining 583FUND_CF component interface 500, 526FUND_CF, component interface 5FUND_DEFINITION component 500,526

FUND_STATUS PSnVision report,configuring 581

FUNDBL_RCN_DEFN component 578

GGain and Loss ChartFields page -Revaluation Step 286

Gain and Loss ChartKeys page - TranslateWithin Ledger 297

Gain and Loss ChartKeys page - TranslationStep 293

GASB 34/35, statutory reporting 500general ledger

budgets, understanding 421business process maps 465business processes 1, 20component interface table 4, 23defining business units 25EPM Budgeting 8.3, integrating 75file import processes 65getting started 1implementing 4, 23integrations 2, 21navigating 11

General Ledgercompanion PeopleBooks xxxi

General Ledger Activity report,GLS7002 609

General Ledger business unitDefinition page 28VAT Defaults page 246

General Ledger Business Unit ID Numberspage 28–29

General Ledger Definition componentApproval Options page 35Currency Options page 34Definition page 28Journal Options page 26, 31

General Ledger Definition component(BUS_UNIT_TBL_GL) 27, 30, 34–35,243

General Ledger PeopleBookcommon elements xxxii

general ledger, VAToptions and defaults 243


Index

prerequisites 238processing transactions 237understanding setup 237

Generic Start Schema 492GL MultiCurrency Group page -MultiCurrency Group 298

GL Process Date page 205GL_AA_EDIT process 49GL_ACCOUNT component 243, 500,526

GL_ADB_CALCX process 49GL_ADB_POST process 61GL_FILE_IMPORT, URL definition 65GL_JEDIT process 58GL_JRNL_COPY process 57GL_JRNL_IMP process 57GL_LED_IMP process 57GL_LED_IMP, importing information 77GL_LED_LOAD process 60GL_SUML process 62GLC1000, Summary Ledger Definitionreport 603

GLC4001, Summary Calendarsreport 603

GLC4003, Combination Group report 603GLC4008, Journal Class report 603GLC5501, ADB Calculation report 603GLC6001, Allocation Group report 603GLC7501, Journal Entry Detail report 604GLJE, creating, processing entry eventjournals 486

glossary 615GLPCLOSE process 51GLPOCONS process 56GLPPOITM process 61GLPPPOST process 60GLPQEQTX process 56GLS1001 report 604GLS1002, Closing Rules report 604GLS1003, Closing Trial Balancereport 604

GLS1004, Journal Closing Statusreport 604

GLS1005, Translate Ledger Reconciliationreport 605

GLS1006, Ledger In-Sync report 605GLS2000, Elimination Set Definitionreport 605

GLS2000, Elimination Sets 357

GLS2001, Minority Interest Set Definitionreport 605

GLS2001, Minority Interest Sets 357GLS2002, Consolidation Definition 358GLS2002, Consolidation Set report 606GLS2003, Consolidation Out of Balancereport 606

GLS2003, Out of Balance 358GLS2004, Minority Interest Eliminationsand Adjustments report 606

GLS2004, Minority Interest/Elimination/Adjustment 358

GLS2005, Audit Elimination Sets Auditreport 606

GLS2006, Equitization Rules 358GLS2006, Equitization Rules report 606GLS2007, Ownership Set 358GLS2007, Subsidiary Ownership Setsreport 606

GLS2008, Equitization CalculationLog 358

GLS2008, Equitization Calculation Logreport 607

GLS3000, Open Item Listing report 607GLS3001, InterUnit Activity report 607GLS4000, Schedules report 607GLS4002, Combination Rule report 607GLS5000, Translation Definitionreport 607

GLS5001, Revaluation Definitionreport 608

GLS5002, Translation Calculation Logreport 608

GLS5003, Revaluation Calculation Logreport 608

GLS5004, Translate in Ledger CalculationLog report 608

GLS5005, Translate in Ledger report 608GLS5500, ADB Definition report 608GLS6000, Allocation Step report 608GLS6002, Allocation Calculation Logreport 608

GLS6003, Budget Copy CalculationLog 609

GLS7001, Standard Journals report 609GLS7002, General Ledger Activityreport 609

GLS7003, Ledger Summary report 609GLS7009, Posted Journal Summaryreport 609


Index

GLS7010, Ledger vs Journal Integrityreport 609

GLS7011, Journal Edit Errors report 609GLS7012, Trial Balance report 610GLS7015, Journal Suspense Activityreport 610

GLS7016, Ledger Activity with Attributesreport 610

GLS7017, Ledger with Attributesreport 610

GLS7500, Ledger File Creation 610GLS8012, Journal Like/Accounting EntryReconciliation report 610

GLS8310, FACTS I Validation report 610GLS8311, FACTS I Trial Balancereport 611

GLS8312, FACTS II Trial Balance 611GLS8400, SF224 Transaction Report 611GLS850, Federal Trial Balance report 611GLS8501, Federal Transaction Registerreport 611

GLS9500, Fund Balance Reconciliationreport 612

government reporting 497prerequisites 503, 528

HHCM account code integration 74HR_ACCT_CD process 57HRMS Account Code Interfaceprocess 57

Human Capital Management (HCM),integrating with general ledger 67

Hyperion Essbase 491

Iimplementation

general ledger 23import

PeopleSoft Budgeting data 75imported accounting entries,inquiring 418

importingcommitment control budget journals 77external VAT data 253flat files, journals 76information to a ledger,GL_LED_IMP 77

journal entries 76

journals, entry events 484spreadsheets, entry events 484VAT, pages used to important fromthird-party systems 254

In-Sync report 307Incremental Calculation Methodpage 28–29

indexescreating 85determining those used 87identifying 86in sample system 92optimizing 100selecting 87suggestions for better indexes 91updating statistics 101

inquiries, three-dimensional 491inquiry

across ledgers by period 415detail header and journal lines 403imported accounting entries 417journal 395journal lines 406ledger details 404ledger summary balances 401ledger transaction details 402ledger, journal, financialinformation 393

ledgers 397INSTALLATION component 67Installation Options component(INSTALLATION) 67

instances, adding non-shared tables 83integrating and transferring information,GLS9003.SQR 77

integrationHCM account code 74

integration, applications 63integrations

activating 68general ledger 2, 21

inter/intraunitallocations 235consolidation 235copy journal 235flat file 236general ledger 233journal edit 234journal entry 235spreadsheet journal import 236


Index

suspense correction 234intercompany

See inter/intraunit 233intercompany investments, calculatingminority interests 313

intercompany transactions,eliminating 311

interim closinginterpreting results 371overview 365procedure 370reports 390understanding 369undoing 389

InterUnit Activity report, GLS3001 607interunit journal entries, entry events 481InterUnit, making entries 143intracompany

See Inter/IntraUnit 233IU_INTER_TMPLT, componentinterface 6

IU_INTRA_TMPLT, componentinterface 6

IU_PAIRS_MAINT, componentinterface 6

Jjournal

criteria 395header and detail lines, inquiry 403header details, inquiry 396lines, inquiry 406pages to review journalinformation 395

view information 395journal approvals, virtual approver 470Journal ChartField Errors page 215Journal Class report, GLC4008 603Journal Closing Status report,GLS1004 604

journal closing status, reportgenerating 390

Journal Copy process 57Journal Copy Req page - CopyJournal 154

Journal Edit Errors report, GLS7011 609Journal Edit process 58Journal Edit Request page 201journal edit, inter/intraunit 234journal entries

approval options 142budget checking errors 458calculate amount process 124calculating 132calculation rule 132copy down options 137copying 154currency defaults 115deleting 159editing 154entry events 484entry template 135errors 141exchange rate 127header page 112importing 76, 159Inter/IntraUnit 143Inter/IntraUnit pages 144intercompany 143intracompany 143intraunit entries, creating 145journal import process 171Lines page 119manual exchange rate, entering 127mask 108pages used 111processing selection 123projects information 137retrieve a system rate 127reversal options 116secondary ledger lines 138security 107separate debit and credit 126set up Inter/IntraUnit Balancing 144SJE 147spreadsheet journal import 171standard entries pages 148standard journal entries 147statistical 37

See Alsostatistical journal entriesstatistics codes 139summary ledger staging tables 146summary ledgers 146system rate 127totals page 139user preferences 107using statistic codes 40view errors 141

journal entries, archivingand restoring 445


Index

journal log, viewing 446pages used to archive and restore 445

journal entries, commitment control 451options 119

journal entries, copyjournal dates 157pages used to copy journals 155

journal entries, creating 107, 110interunit entries 146

journal entries, file importflat file import 159importing journals from flat file 170setting up 159

journal entries, General LedgerCommitment Control 450

journal entries, separate debit/creditentry events 483

journal entrystatistics 38

journal entry approvalnavigation 470security 468setting up workflow 468understanding 465using workflow 465virtual approver 467workflow definition 466

journal entry approval workflowapproval 600denial 599process 599

Journal Entry componentApproval page 142Errors page 141Header page 112Lines page 119Totals page 139using 110

Journal Entry Detail Report with Attributes,FIN2005 602

Journal Entry Detail report, FIN2001 602Journal Entry Detail report, GLC7501 604journal entry, Commitment Control

overriding the data 457overriding user ID 457using entry events 458

journal entry, copyjournal process 155

journal error processing optionsamount suspense ChartFields 34

balance suspense ChartField page 34balance suspense ChartFields 33control total 32edit suspense ChartFields 33journal amount errors 32journal balance 31journal edit errors 32

journal generatorloading accounting entries 66PeopleSoft applications 66third-party applications 67

Journal Generator process 59journal header, budget exceptions

budget exceptions 460journal line details, drilling down 462Journal Line Template page 214Journal Line/Accounting EntryReconciliation report 610

journal linesscrolling 122

journal lines, Commitment Control,entering and processing 457

Journal Options page - ConsolidationDefinition 329

Journal Options page - General LedgerDefinition 26, 31

Journal Post process 60journal processing

options, journal process date 32understanding 189

Journal Source component(SOURCE) 243

journal source VAT defaults 247Journal Suspense Activity report 610Journal Suspense Correction page 210journal workbook defaults, setting 178journal worksheets

importing in batch mode 185importing online 184

journalsarchiving and restoring 445copying 154correction journals 219defining standard entries 148deleting 159determining the status 197entering 183entry errors, viewing 141header information, entering 112identifying 108


Index

line details, viewing 199line information, entering 119process date, setting 205standard entries, inquiring 152understanding processing 190unlocking 219unposting 209

journals, creating 107standard entry 147, 150VAT 249

journals, edits 154correcting errors 203requesting 200

journals, entriesfinding errors 203marking for posting 206

journals, posting 204checking status of requests 208requesting 207

journals, processing 109, 189date 26, 31

journals, specifyingapproval options 142entry totals 139processing options for a businessunit 30

journals, suspense 197, 219correction lines, viewing errors for 218correction option 210

LLearning Solutions(LS), integrating withgeneral ledger 67

Led Load Rqst page 362ledger

compare periods, navigation pages 410comparing two across periods 413summary balances, inquiry 401

Ledger Activity with Attributes report,GLS7016 610

Ledger and TimeSpan page - TranslateWithin Ledger 295

ledger balances, preparing to translate 287ledger cube, OLAP 494ledger data, publish and subscribe 77Ledger File Creation 610Ledger Groups component(DETAIL_LEDGER_GROU) 143

Ledger In-Sync report 307GLS1006 605

ledger interface utility 359Ledger Load process 60Ledger Summary report, GLS7003 609Ledger vs Journal Integrity report,GLS7010 609

Ledger with Attributes report 610ledger, inquiry 397

criteria 399details 404groups 405navigation pages 405pages to review ledger information 398summary and detail, configuring 407transaction details 402

LEDGER_SET component 320ledgers

archive ledger log, viewing 444archiving and restoring 441–442consolidations transferring 77loading external data 362sending 359

ledgers, comparingacross periods navigation pages 414by period 412comparison criteria 414period compare, search criteria 410periods 409

Lines page - Journal Entry 119

MMAF

FACTS I 523MAF data

FACTS II 546reviewing 547

mapping business processes 465Mark for Post page 206Mark for Unpost page 209marking journals for unposting 209MBXLAT component 294Message Log 44

restarting and recovering process 45Message Log report, FIN1001 601messages

accounting entry 74Commitment Control budget update 74

messages, transaction and others 74Minor Int Elim Ad page 358Minor Int Sets page 357Minor Int Source page 327


Index

Minor Int Target page 328Minority Interest Eliminations andAdjustments report, GLS2004 606

Minority Interest page - EquitizationRules 352

Minority Interest Set Definition report,GLS2001 605

Minority Interest Sets componentMinor Int Source page 327Minor Int Target page 328

Minority Interest Sets component(MINORITY_INTEREST) 325

minority interestscalculating 313creating entries 345defining sets 325defining sources 327specifying 352

MINORITY_INTEREST component 325Miscellaneous ChartFields component(F2_ELEMENT_CF) 500, 526

multibook ledgers, entry events 481MultiCurrency Group component, GLMultiCurrency Group page 298

MultiCurrency group, defining 298MultiCurrency processing

in MultiBook environment 301initiating 299request page 299scenarios 301

MultiCurrency Processing 61multicurrency, open item reconciliation andclosing 231

multiple parent/subsidiary ownershipexample 345

Nnavigation

copy budgets 433general ledger 11journal entry approval workflow 470maintain detail budgets 427project budgets, maintaining 432

Net Income/Retained Earnings page 380non-shared tables

adding instances 83setting up 82understanding 80using in COBOL SQL Batchprocesses 79

notes xxviii

OOLAP

analyzing cube data 496building cubes 494database 492defining the cube 493planning 492preparing trees and queries 492tools, using 491understanding 491

open itemaccount 224accounting, understanding 223closed item 224closing 227creating transactions 226definition 224key 224navigation pages 226processing transactions 226re-opening 231reviewing reconciled 231setting up prompt table 225tolerance amount 224transactions, processing andentering 225

Open Item Listing report, GLS3000 607open item reconciliation and closing

detail level 230multicurrency rows 231

Open Item Reconciliation process 61open item transactions, navigationpages 228

open item, reconciliationbalances 227GLPOITM 228manual 228

OPER_UNIT_CF, component interface 7operational structure

defiining 25OPR_DEFAULT_FIN, componentinterface 7

optimization, performance 79optimizing general ledgerperformance 79, 85

OraclePS journal line 100PS ledger 95


Index

Out Of Balance Rp page 358Output and Journal Options page -Revaluation Step 282

Output and Journal Options page - TranslateWithin Ledger 297

override amount, Commitment Controljournal entry 457

override date, Commitment Control journalentry 457

override user ID 457overriding journal entry amount 457Ownership page 358ownership sets, defining 348

Ppartition IDs 102PeopleBooks

ordering xxviPeopleCode, typographicalconventions xxvii

PeopleSoft application fundamentals xxvPeopleSoft Budgeting

importing data 75PeopleSoft Cube Manager 491, 493performance

enhancement prerequisites 79optimizing General Ledger 79optimizing PS/nVision 104physical considerations 102

Period 998 Adjustments 264physical usage, processes 45planned field, selecting CommitmentControl amount type 456

Post Daily Balance process 61post date, defining 205Posted Journal Summary report,GLS7009 609

posted total amount 394posted total base amount 394posted total transaction amount 394pre-encumbrance, selecting CommitmentControl amount type 456

preparer file, FACTS II 532prerequisites xxv

Average Daily Balances (ADB) 255budgets, standard 421FACTS I 503FACTS II 528general ledger VAT 238government reporting 503, 528

performance enhancement 79spreadsheet journal import 173

printed documentation xxviprocess date, and journal processing 26,31

process instance 44processes

application pages, initiating from 43,45

background 43concurrency 48FS_ALLC, Allocations 48FS_CEDT_PROC, ChartFieldCombination Editing 51

FS_JGEN, Journal Generator 59FSPCCURR, MulticurrencyProcessing 61

FSPKBDP3, Commitment ControlBudget Processor 52

FSPQPOST, Commitment ControlBudget Post 52

FSPYCLOS, Commitment ControlBudget Closing 52

functional usage 45GL_AA_EDIT, Alternate AccountEdit 49

GL_ADB_CALCX, Average DailyBalance Calculation 49

GL_ADB_POST, Post DailyBalance 61

GL_JEDIT, Journal Edit 58GL_JRNL_COPY, Journal Copy 57GL_JRNL_IMP, Flat File JournalImport 57

GL_LED_IMP, Flat File LedgerImport 57

GL_LED_LOAD, Ledger Load 60GL_SUML, Summary Ledger 62GLPCLOSE, Closing 51GLPOCONS, Consolidations 56GLPPOITM, Open ItemReconciliation 61

GLPPPOST, Journal Post 60GLPQEQTZ, Equitization 56HR_ACCT_CD, HRMS Account CodeInterface 57

physical usage 45restarting and recovering 43, 45running concurrently 45

processing


Index

FACTS II 528journals 189multiple currencies 277undo close 389undoing an interim close 389

producing ADB reports 275PRODUCT_CF, component interface 7PROGRAM_CF, component interface 7project budgets

maintaining 431maintaining, navigation pages 432reviewing and modifying 432

PROJECT_CF, component interface 7PS journal header 96–97PS journal line 99PS ledger 95PS_FILEDIR, environmental variable 65PS/nVision, optimizing performance 104PSTREEMGR component 506, 549, 581Publish Ledger page 362

Rreconciliation

Fund Balance 578open item (GLPOITM) 228

Reconciliation by ChartField,FIN5005 603

Reconciliation by System Source,FIN5001 602

Reconciliation Rpt Definition component(FUNDBL_RCN_DEFN) 578

reconciling open item balances 227recycle, and journal errors 26, 31regular balance 393Reimbursable Agreement Accountcomponent (RMC18_SETUP) 586

reimbursable agreement account, setting upin General Ledger 586

related documentation xxvireport, generating

translation definition 306report, GLC

GLC4008, Journal Class 603GLC5501, ADB Calcuation 603

reporting, Federal Government 497FACTS I 501FACTS II, overview 527Fund Balance Reconciliationoverview 578

overview, FACTS I trees 501

processing FACTS II overview 528processing, FACTS I overview 503setting up FACTS I, overview 501setting up FACTS II, overview 527

reporting, financial statement, XBRL,overviewXBRL, overview 500

reporting, statutory, GASB 34/35 500reports

Calculation Log 306Closing Rules 390Closing Trial Balance 390Consolidation Definition 358Elimination Sets 357FACTS II Trial Balance 611General Ledger Activity, GLS7002 609generating closing rules 390Interim and year end Closing 390Journal Closing Status 307, 390journal edit errors 221Journal Line/Accounting EntryReconciliation 610

Journal Suspense Activity 610Ledger File Creation 610Ledger Summary, GLS7003 609Ledger vs Journal Integrity,GLS7010 609

Ledger with Attributes 570, 610Minority Interest Sets 357Minority Interest/Elimination/Adjustment 358

Out Of Balance 358Ownership Set 358posted journal summary 221producing journal reports 220producing revaluation andtranslation 305

revaluation calculation log 306revaluation definition 306running concurrently 45Standard Journals 609Statement of Accountability,SF1219 613

suspended activity 221Translate in Ledger 608Translate Ledger Reconciliation 307translate within ledger step 306translation definition 306translation within ledger calculationlog 306


Index

reports, EquitizationCalculation Log 358GLS2006 606GLS2008, Equitization CalculationLog 607

Rules 358reports, FACTS I

Trial Balance 611Validation 610

reports, FINFIN1001, Message Log 601FIN2001, Journal Entry Detailreport 602

FIN2005, Journal Entry Detail Reportwith Attributes 602

FIN5001, Reconciliation by SystemSource 602

FIN5005, Reconciliation byChartField 603

reports, generatingclosing trial balance 390journal edit errors 221revaluation calculation log 306revaluation definition 306suspended activity 221translate within ledger step 306translation calculation log 306translation ledger reconciliationreport 307

translation within ledger calculationlog 306

reports, GLCGLC1000, Summary LedgerDefinition 603

GLC4001, Summary Calendars 603GLC4003, Combination Group 603GLC6001, Allocation Group report 603GLC7501, Journal Entry Detail 604

reports, GLSGLS1001, Summary Ledger Detail 604GLS1002, Closing Rules 604GLS1003, Closing Trail Balance 604GLS1004, Journal Closing Status 604GLS1005, Translate LedgerReconciliation 605

GLS1006, Ledger In-Sync 605GLS2000, Elimination SetDefinition 605

GLS2001, Minority Interest SetDefinition 605

GLS2003, Consolidation Out ofBalance 606

GLS2004, Minority Interest Eliminationsand Adjustments 606

GLS2005, Audit Elimination SetsAudit 606

GLS2006 606GLS2007, Subsidiary OwnershipSets 606

GLS2008, Equitization CalculationLog 607

GLS3000, Open Item Listing 607GLS3001, InterUnit Activity 607GLS4000, Schedules 607GLS4002, Combination Rule 607GLS5000, Translation Definition 607GLS5001, Revaluation Definition 608GLS5002, Translation CalculationLog 608

GLS5003, Revaluation CalculationLog 608

GLS5004, Translate in LedgerCalculation Log 608

GLS5500, ADB Definition 608GLS6000, Allocation Step Report 608GLS6002, Allocation CalculationLog 608

GLS6003, Budget Copy CalculationLog 609

GLS7009, Posted JournalSummary 609

GLS7011, Journal Edit Errors 609GLS7012, Trial Balance 610GLS7016, Ledger Activity withAttributes 610

GLS8400, SF224 Statement of CashTransaction Details 612

GLS8400, SF224 TransactionReport 611

GLS8500, Federal Trial Balance 611GLS8501, Federal TransactionRegister 611

GLS9002, Consolidation Set 606GLS9500, Fund BalanceReconciliation 612

reports, SFGLS8400, SF224 Statement of CashTransaction Details 612

GLS8400, SF224 TransactionReport 611


Index

SF1219 571SF1220, Statement of TransactionsClassified by Appropriation, Fund, andReceipt Accounts report 613

SF224, Statement of CashTransactions 612

SF224/1220 571–572Request - MultiCurrency Processing 299Request page - Journal Edit 201request records 44restoring

archived journals 446archived ledger date 443

retained earnings accountclosing to multiple 367closing to single 366

REVAL_STEP component 279revaluation

calculation log report,understanding 306

defining steps 279definition report, generating 306gain and loss ChartFields,specifying 286

ledger and TimeSpan, specifying 280revaluation calculation log report,generating 306

setting up 278specifying ChartFields for 281specifying output and journal optionsfor 282

using in a MultiBook environment 301Revaluation Calculation Log report,GLS5003 608

Revaluation Definition report,GLS5001 608

Revaluation Step component(REVAL_STEP) 279

Revaluation Step page groupGain and Loss ChartFields page 286Output and Journal Options page 282

reversal, ADB 118RMC18_SETUP component 586Roll Forward Options page 385rule set definition, modifying workflowitem 472

SSchedules report, GLS4000 607schedules,setting up 150

search criteria, compare ledger perioddata 410

security, approving journal entriesapproving journal entries 468

SECURITY_BU_CLS, componentinterface 7

SECURITY_BU_OPR, componentinterface 8

SECURITY_CF_PAGELET, componentinterface 6

SECURITY_LEDGER_CLS, componentinterface 8

SECURITY_LEDGER_OPR, componentinterface 8

SECURITY_NVISION_LEDGER,component interface 6

SET_CNTRL_TABLE1 component 506,549

SF1219 reportdefining 571generating 577navigation pages 572understanding 571

SF1219 Report Definition component(SF1219_DEFN) 571

SF1219, Statement of Accountability 613SF1219/1210 Flat File, Creating 578SF1219_DEFN component 571SF1220 report 613SF1220 report, printing 578SF224 report 612

printing, creating file 577SF224 Statement of Cash TransactionDetails, GLS8400 612

SF224 Transaction Report, GLS8400 611SF224/ SF1220 Report Defn component(SF224_SF1220_DEFN) 571

SF224/1220 reportdefining 571generating 575navigation pages 572understanding 571

SF224_SF1220_DEFN component 571Shared Table Statistics page 82SJE

See standard journal entries 147SJE Status page 152SOURCE component 243Source page - Equitization Rules 349spreadsheet journal entry


Index

overview 173using 173

spreadsheet journal import 76entry events 484prerequisites 173process, using 171

Spreadsheet Journal Import Batch Process(GL_EXCL_JRNL) 186

spreadsheet journalsentering 183importing 175setting up 175

SQL statements, capturing 86, 106SQR reports, running concurently 45standard budgets

allocation process 425ChartFields 427copy process 425creating 422maintaining 421–422percentage increases 423repeating 423spreading 423understanding 421

standard journal entriesamount spread 153creating 147defining 148entry events 483pages used 148running the process 153schedules, setting up 150status 152viewing status 152

Standard Journal Entry page 150Standard Journals report, GLS7001 609Statement of Accountability report,SF1219 613

Statement of Cash Transactions,SF224 612

Statement of Transactions Classifiedby Appropriation, Fund, and ReceiptAccounts report, SF1220 613

statistical journal entriescreating 40overview 37setting up 38

statistics code method 38statistics codes, using 139statistics, using 37

STATISTICS_CODE, componentinterface 8

status codes, commitment control 460statutory reporting, GASB 34/35, overview

GASB 34/35, overview 500subsidiaries

defining ownerships 325equitizing activities in 344specifying offsets for 351

Subsidiary Offset page - EquitizationRules 351

Subsidiary Ownership component(CONSOL_OWNERSHIP) 325

Subsidiary Ownership Sets report,GLS2007 606

subsystem accounting entries, drillingdown 404

suggestions, submitting xxixSummary Calendars report,GLC4001 603

summary inquiry options, adding 408Summary Ledger Definition report,GLC1000 603

Summary Ledger Detail report,GLS1001 604

Summary Ledger process 62summary ledgers

defining consolidation sets 338defining consolidation sets on 338defining elimination sets forconsolidations 337

defining minority interest sets forconsolidations 338

updating incrementally 103suspend, and journal errors 26, 31suspense and correction journals,postingand unposting 219

Suspense Cross Reference page 218suspense cross references, inquiring 218suspense journals 219

correcting entry events 489understanding 197

sync data, publishing 73

Ttable seeding 101tableset control

record group 520, 561tree 522, 562


Index

TableSet Control component(SET_CNTRL_TABLE1) 506,549

tableset control, FACTS I 520Target page – Equitization Rules 350TAX_AUTHORITY_VAT, componentinterface 8

TAX_BU_CODE_VAT, componentinterface 8

TAX_CODE_VAT, componentinterface 9

terms 615third-party applications, journalgenerator 67

TimeSpan and Rate page - TranslationRule 288

Totals - Journal Entry 139TRANS_RULE component 288TRANS_STEP component 290transaction amount 394transaction partner tree 558transfer account tree 557transfer agency tree 556transferring and integrating information

GLS9003.SQR, using 77Translate in Ledger report, GLS5005 608Translate Ledger Reconciliation report,GLS1005 605

Translate Within Ledger componentGain and Loss ChartKeys 297Output and Journal Options page 297

Translate Within Ledger page groupChartfields page 296Ledger and TimeSpan page 295

translate within ledger processafter revaluation 303specifying a ledger and TimeSpan 295

Translate Within Ledger processpreparing for 294

translationcalculation log report 306definition report 306gain and loss ChartKeys,specifying 293

journal options, specifying 292ledger reconciliation report 307output options, specifying 292translation ledger within multi-book,required ledger structure 307

Translation Calculation Log report,GLS5002 608

Translation Definition report,GLS5000 607

Translation in Ledger Calculation Logreport, GLS5004 608

translation ledger results, MultiBook insingle book environment 304

Translation Rule - Chartfields page 289Translation Rule component(TRANS_RULE) 288

Translation Rule component group,Chartfields page 289

Translation Rule page group, TimeSpan andRate page 288

translation rulesdefining ChartFields for 289setting up 288specifying 291TimeSpans and rates, defining 288

Translation Step component(TRANS_STEP) 290

Translation Step component, Gain and LossChartKeys page 293

translation steps, defining 290translation within ledger

calculation log report, generating 306calculation log report,understanding 306

output and journal options,specifying 297

specifying Chartfields for 296specifying gain and loss ChartKeysfor 297

step report 306Translation Within Ledger component(MBXLAT) 294

Treasury Symbol Cross Ref component(F2_TSYM_XREF) 526

treasury symbol, cross-reference,setup 549

treeacccounts requiring attributes, FACTSI 517

account roll-up, FACTS II 552account, FACTS I 510–511accounts requiring fund attributes tree,FACTS II 554

budget subfunction/account, FACTSI 514


Index

bureau, FACTS I 508category B, FACTS II 553cohort year, FACTS II 553custodial/acct, FACTS I 513exchange/acct, FACTS I 512fund group, FACTS I 509tran partner, FACTS I 515transaction partner tree, FACTS II 558transaction partner/acct., FACTS I 516transfer account tree, FACTS II 557transfer agency tree, FACTS II 556

tree groupFACTS I 518FACTS II 560

tree joins 105Tree Manager component(PSTREEMGR) 506, 549, 581

trees 317See AlsoconsolidationsChartField data, rolling up 551FACTS II, creating 549FACTS II, overview 527

Trial Balance report, GLS7012 610typographical conventions xxvii

Uunit of work 43unpost journal date, changing 194URL definition, GL_FILE_IMPORT 65user ID, override 457user preferences, defining 107using statistics 37

Vvalidating data, FACTS II 569validation checking 388VAT

account options, setting up 248default options, general ledger 246default options, setting up journalsource 247

default processing hierarchy 239drivers, general ledger 244general ledger prerequisites 238GL journal entry 251journal entries, navigation pages 250journal line data 250journals, creating and processing 249

processing transactions in generalledger 237

setting up defaults, general ledger 244setup, navigation pages 244understanding general ledger setup 237using GL_JRNL_IMP 254

VAT Defaults Sub-Search component(VAT_DEFAULT_SEARCH) 243

VAT options, specifying for businessunit 27

VAT, importingfrom third-party systems 253journal lines 254

VAT_DEFAULT_SEARCHcomponent 243

VAT_ENTITY_ID, componentinterface 9

virtual approver 470journal entry approval 467

visual cues xxviii

Wwarnings xxixwhere clause, SQL 89workbook defaults, setting 178workflow

approval properties, modifying 471approvals 470approving journal entries 465business process maps 465definition, journal entry approval 466General Ledger 599journal entry approval process 599rules, defining 473

workflow itemdefining journal entry approvalrules 473

modifying rule set definition 472setting up events 474

XXBRL

overview 500XBRL Context component(XBRL_CONTEXT) 588

XBRL Element component(XBRL_ELEMENT) 588

XBRL Instance Template component(XBRL_SETUP) 588


Index

XBRL NameSpace component(XBRL_SETUP_NSPACE) 588

XBRL_CONTEXT component 588XBRL_ELEMENT component 588XBRL_SETUP component 588XBRL_SETUP_NSPACEcomponent 588

Yyear end closing 372

interpret results 374overview 365procedure 373procedures checklist 372producing reports 390undoing 389


Index


PeopleSoft General Ledger8.8 Reports

December 2003

PeopleSoft General Ledger 8.8 ReportsSKU FSCM88GLR-R 1203Copyright © 1992-2003 PeopleSoft, Inc. All rights reserved.

All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc. ("PeopleSoft"), protected by copyright laws and subject tothe nondisclosure provisions of the applicable PeopleSoft agreement. No part of this documentation may be reproduced, stored in a retrieval system,or transmitted in any form or by any means, including, but not limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise withoutthe prior written permission of PeopleSoft.

This documentation is subject to change without notice, and PeopleSoft does not warrant that the material contained in this documentation is free of errors.Any errors found in this document should be reported to PeopleSoft in writing.

The copyrighted software that accompanies this document is licensed for use only in strict accordance with the applicable license agreement which should beread carefully as it governs the terms of use of the software and this document, including the disclosure thereof.

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registered trademarks, and Pure Internet Architecture,Intelligent Context Manager, and The Real-Time Enterprise are trademarks of PeopleSoft, Inc. All other company and product names may be trademarks oftheir respective owners. The information contained herein is subject to change without notice.

Open Source Disclosure

PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability ordamages resulting from use of said software or documentation. The following open source software may be used in PeopleSoft products and the followingdisclaimers are provided.

Apache Software Foundation

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache SoftwareFoundation. All rights reserved.

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALLTHE 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 ORSERVICES; 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 THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

OpenSSL

Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; 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 THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

SSLeay

Copyright (c) 1995-1998 Eric Young. All rights reserved.

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NOEVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Loki Library

Copyright (c) 2001 by Andrei Alexandrescu. This code accompanies the book:

Alexandrescu, Andrei. "Modern C++ Design: Generic Programming and Design Patterns Applied". Copyright (c) 2001. Addison-Wesley. Permission to use,copy, modify, distribute and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copiesand that both that copyright notice and this permission notice appear in supporting documentation.

Contents

Reports PrefaceAbout This PeopleBook ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vRelated Documentation. . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . v

Obtaining Documentation Updates. . .. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . vOrdering Printed Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . v

Comments and Suggestions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1PeopleSoft General Ledger Reports. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PeopleSoft General Ledger Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2Report Samples... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

PeopleSoft Proprietary and Confidential iii

Contents

iv PeopleSoft Proprietary and Confidential

About This PeopleBook

PeopleBooks provide you with the information that you need to implement and use PeopleSoft applications.


• Related documentation.

• Comments and suggestions.

Related DocumentationThis section discusses how to:

• Obtain documentation updates.

• Order printed documentation.

Obtaining Documentation UpdatesYou can find updates and additional documentation for this release, as well as previous releases,on the PeopleSoft Customer Connection web site. Through the Documentation section ofPeopleSoft Customer Connection, you can download files to add to your PeopleBook Library.You’ll find a variety of useful and timely materials, including updates to the full PeopleSoftdocumentation that is delivered on your PeopleBooks CD-ROM.

Important! Before you upgrade, you must check PeopleSoft Customer Connection for updates to theupgrade instructions. PeopleSoft continually posts updates as the upgrade process is refined.

See Also


Ordering Printed DocumentationYou can order printed, bound volumes of the complete PeopleSoft documentation that is deliveredon your PeopleBooks CD-ROM. PeopleSoft makes printed documentation available for eachmajor release shortly after the software is shipped. Customers and partners can order printedPeopleSoft documentation by using any of these methods:

• Web

• Telephone

• Email

PeopleSoft Proprietary and Confidential v

Reports Preface

Web

From the Documentation section of the PeopleSoft Customer Connection web site, access the PeopleSoftPress web site under the Ordering PeopleBooks topic. The PeopleSoft Press web site is a joint venturebetween PeopleSoft and Consolidated Publications Incorporated (CPI), the book print vendor. Use acredit card, money order, cashier’s check, or purchase order to place your order.

Telephone

Contact CPI at 800 888 3559.

Email

Send email to CPI at [email protected].

See Also


Comments and SuggestionsYour comments are important to us. We encourage you to tell us what you like, or whatyou would like to see changed about PeopleBooks and other PeopleSoft reference andtraining materials. Please send your suggestions to:

PeopleSoft Product Documentation Manager PeopleSoft, Inc. 4460 Hacienda Drive Pleasanton, CA 94588

Or send email comments to [email protected].

While we cannot guarantee to answer every email message, we will pay careful attentionto your comments and suggestions.

vi PeopleSoft Proprietary and Confidential

CHAPTER 1

PeopleSoft General Ledger Reports

This appendix provides an overview of PeopleSoft General Ledger reports and enables you to:

• View summary tables of all reports.

• View report details.

Note. For samples of these reports, see the Portable Document Format (PDF) fields thatare published on CD-ROM with your documentation.

PeopleSoft General Ledger ReportsThis table lists the PeopleSoft General Ledger reports, sorted alphanumerically by report ID. If you needmore information about a report, refer to the report details at the end of this appendix.



FIN1001Message Log Report

Prints message logs for aprocess instance ID and batchreport type, similar to theonline query available foreach background program.Displays job ID, programname, date, time, sequencenumber, logged message, andexplanation for each processinstance ID. (SQR)

General Ledger, MonitorBackground Processes,Background Process Report

RUN_FIN1001


PeopleSoft General Ledger Reports Chapter 1



FIN2001Journal Entry Detail Report

Displays all journal entriesentered in the system fora business unit and ledgerwithin the date rangespecified. Prints the journalentries in ascending IDorder within the ledger andshows the journal date, thesource, whether a reversalentry was created, journalstatus, posted date (if any),and a description. For eachline included in the journalentry, lists the line numberof the entry, the accountnumber, a description,the department, product,and project ChartFieldvalues, and debit and creditdetail. Also prints statisticalinformation where includedin a journal entry. (SQR)

General Ledger, GeneralReports, Journal Entry Detail

RUN_FIN2001

FIN2005Journal Entry Detail Reportwith Attributes

This report is similar to theJournal Entry Detail Report,except this report also liststhe ChartField attributevalues. (SQR)

General Ledger, GeneralReports, Journal Entry withAttributes

RUN_FIN2005

FIN5001Reconciliation by SystemSource

This report consists ofdetailed subsystem and GLjournal transactions that areaggregated to the businessunit, subsystem source,ledger, account or alternateaccount, fiscal year andaccounting period level.

For example, it lists the dataat the system source level,such as AP, and then lists allthe activity for AP, includingwhat was posted and notposted, for one or moreselected ChartFields thatappear in the data that youloaded. (SQR)

General Ledger, GeneralReports, GL ReconciliationSubsystem, Reconciliationby System Srce (source)

RUN_FIN5001


Chapter 1 PeopleSoft General Ledger Reports



FIN5005Reconciliation by ChartFieldreport.

This report lists the databased on one or moreselected ChartFields thatappear in the data thatyou loaded. Each of thesubsystem amounts thatfall within the ChartFieldcombination is listed on thereport along with the totalamounts for the ChartFieldsand the related ledgers.(SQR)

General Ledger,General Reports, GLSubsystem Reconciliation,Reconciliation byChartFields

RUN_FIN5005

GLC1000Summary Ledger DefinitionReport

Displays information aboutsummary ledgers, includinga description, the detailledger it summarizes, recordnames, and a listing of theChartFields associated withthe ledger. (Crystal)

General Ledger, SummaryLedgers, Summary LedgerDefinition Rpt (report)

RUN_GLC1000

GLC4001Summary Calendars

Displays information aboutsummary calendars. Includesa description as well as alisting of the periods youhave defined for the calendar.(Crystal)

Setup Financials/SupplyChain, Common Definitions,Calendars/Schedules,Summary Calendar Report

RUN_GLC4001

GLC4003Combination Group

Displays information onChartField combination editgroups for a selected setID.(Crystal)

Setup Financials/SupplyChain, Common Definitions,Design ChartFields,Combination Editing,Combination Group Report

RUN_GLC4003

GLC4008Journal Class Report

Displays journal class nameand a description of each fora selected SetID. (Crystal).

Set Up Financials/SupplyChain, Common Definitions,Journals, Class Report,Journal Class Report

RUN_GLC4008

GLC5501ADB Calculation Report

Lists ADB calculation detailsincluding averaged period,date, and time. (Crystal)

General Ledger, AverageDaily Balance, ADBCalculation Report

RUN_GLC5501

GLC6001Allocation Group

Lists detail informationassociated with a particularallocation group. (Crystal)

Allocations, Reports,Allocation Group

RUN_GLC6001





GLC7501Journal Entry Detail

Shows journal entry detailinformation by business unit,journal ID, date, description,ledger group, source,reversal, foreign currency,rate type, effective date,and effective rate. It alsoshows line number, account,description, amount, ratetype, exchange rate, foreignamount, base amount,and totals for the journal.(Crystal)

General Ledger, Journals,Journal Entry, Create JournalEntries, Journal Entry LinesPage, Select Print Journalvalue in the Process field,and click Process button.

RUN_GLC7501

GLS1001Summary Ledger Detail

This is a template fordesigning reports basedon user-specific ledgerdefinitions. This is basedon the summary ledger(PS_S_LEDGER_SUM),which you can find in theDEMO database. The recorddefinition set consists of thefollowing ChartFields:ACCT, OPERATING_UNIT,DIVISION,PRODUCT_AREA, andPROJ. Contains one statisticscode field named STATS.(SQR)

General Ledger, SummaryLedgers, Summary LedgerDetail Report

RUN_GLS1001

GLS1002Closing Rules

Displays information aboutclosing set rules. It printsa description of the closeset, identifies the name ofthe account ChartField, andshows the ChartField towhich that profit and lossaccount will be closed.Also shows the option forretaining earnings into theChartField. (SQR)

General Ledger, CloseLedgers, Closing RuleReport

RUN_GLS1002

GLS1003Closing Trial Balance

Summarizes all entries onthe ledger by account type.Prints beginning and endingbalances for the year, totalsfor the period, adjustments,and closing entries. (SQR)

General Ledger, CloseLedgers, Closing TrialBalance

RUN_GLS1003

GLS1004Journal Closing Status

Displays the journal linedetails for journal lines withvarious closing statuses.(SQR)

General Ledger, CloseLedgers, Journal ClosingStatus Report

RUN_GLS1004





GLS1005Translate LedgerReconciliation

This report reconciles theamounts in the currencytranslation ledger to theamounts in the primaryledger within a Multibookledger group. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translate Ledger Reconcile

RUN_GLS1005

GLS1006Ledger In-Sync

This report searches thecurrency translation ledgerwithin a multibook ledger tosee if there is any data (for aparticular year) violating therequired ledger structure.(SQR)

General Ledger, ProcessMulti-Currency, Reports,Ledger In-Sync

RUN_GLS1006

GLS2000Elimination Set Definition

Displays all elimination setdefinitions for financialconsolidations. Listsaccounts to whichdifferences will post if theset doesn’t eliminate andshows the ChartFields(such as ACCOUNT andBUSINESS_UNIT) and theChartField values that makeup the elimination set, aswell as a description of thosevalues. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets

RUN_GLS2000

GLS2001Minority Interest SetDefinition

Displays the minority interestset definitions for financialconsolidations. Lists foreach minority interest set adescription, tree structure ID,the subsidiary entity, andpercent of ownership. Alsolists the accounts to whichdifferences will post if the setdoesn’t eliminate, as wellas the ChartField, mannerspecified, tree name/level,and the values that makeup the parent/subsidiaryaccounts. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Minority Interest Sets

RUN_GLS2001





LS2002Consolidation Set Report

Displays the options andcontrols that tell GeneralLedger how to processa consolidation. Lists thejournal ID mask, source,and relative eliminationreversal date for eliminationsjournals, the ChartFieldsincluded in the eliminationjournals, whether or not allelimination sets defined forthe consolidation tree willapply, which eliminationsets will be used, whether allminority interest sets apply,and which minority interestsets will be used. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Consolidation Definition,Consolidation Set Report

RUN_GLS2002

GLS2003Consolidation Out ofBalance Report

Displays the eliminationsets and ledger amountsprocessed for a consolidationrequest. The elimination setsare totaled and any out ofbalance amount is displayed.The out of balance amountsare also summarized at thenode and tree levels. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Out of Balance,Consolidation Out ofBalance Report

RUN_GLS2003

GLS2004Minority InterestEliminations andAdjustments

Displays the results ofminority interest calculationsfor a consolidation requestbased on the combinationof business units present inthe consolidation tree. Theelimination and adjustmententries are grouped byminority interest set. (SQR)

General Ledger,Consolidate FinancialData, Reports, Minority IntElim/Adjustment

RUN_GLS2004

GLS2005Audit Elimination Sets

Displays the eliminationsets and audit informationincluding account andbusiness unit. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Elimination Sets Audit,Audit Elimination Sets

RUN_GLS2005

GLS2006Equitization Rules

Displays the definitioninformation and purposefor the equitization ruleincluding component,ChartField, value, anddescription. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Equitization Rules

RUN_GLS2006

GLS2007Subsidiary Ownership SetsReport

Shows the ownership,set status, effectivedate, description, entityChartField, subsidiaryentity, parent, ownershippercentage, and controllingequitize. (SQR)

General Ledger, ConsolidateFinancial Data, Reports,Ownership Sets, SubsidiaryOwnership Sets Report

RUN_GLS2007





GLS2008Equitization Calculation Log

Lists equitization calculationdetails by process instance.(SQR)

General Ledger, ConsolidateFinancial Data, Reports,Equitization Calculation Log

RUN_GLS2008

GLS3000Open Item Listing

Lists Open Items for theaccounts specified, includinga description of the accounts,the OpenItem key field, and adetailed listing of the journallines that have an open statusup to the As of Date. Thejournal lines are subtotaledby key field value. Journallines containing OpenItemaccounts are matchedtogether based on theOpenItem edit field. (SQR)

General Ledger, Open Items,Open Item Listing Report

RUN_GLS3000

GLS3001InterUnit Activity

Displays reconciliationinformation by businessunit, ChartField, primaryand balancing values, andvariance. (SQR)

General Ledger, GeneralReports, InterUnit Activity

RUN_GLS3001

GLS4000Schedules

Prints a list of the schedulesyou have defined for aSetID. The report includes adescription of each scheduleand the definition of itsfrequency. (SQR)

Setup Financials/SupplyChain, Common Definitions,Calendars/Schedules,Schedules Report

RUN_GLS4000

GLS4002Combination Rule

Displays information ona selected ChartFieldcombination edit rule. (SQR)

Setup Financials/SupplyChain, Common Definitions,Design ChartFields,Combination Editing,Combination Rule Report

RUN_GLS4002

GLS5000Translation Definition

Displays the details andrules of each currencytranslation step. For eachtranslation step, the reportshows the description, ledgerinformation, output andjournal options, and gain andloss ChartKeys. In addition,detailed informationis displayed for everytranslation rule used by thetranslation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation Step, TranslationStep Definition Report

RUN_GLS5000





GLS5001Revaluation Definition

Displays the details of eachcurrency revaluation step,including revaluation stepdescription, ledger andTimeSpan information,exchange rate type, outputand journal options, gain andloss ChartKeys, and detailedrevaluation ChartKeyinformation. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Revaluation Step,Revaluation Step DefinitionReport

RUN_GLS5001

GLS5002Translation Calculation Log

Lists translation calculationdetails by process instanceand translation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation Calculation Log

RUN_GLS5002

GLS5003Revaluation Calculation Log

Lists revaluation calculationdetails by process instanceand revaluation step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Revaluation Calculation Log

RUN_GLS5003

GLS5004Translate in LedgerCalculation Log

Lists translation withinledger calculation details byprocess instance and translatewithin ledger step. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger CalcLog (translation in ledgercalculation log)

RUN_GLS5004

GLS5005Translation in Ledger

Displays the details and rulesof each translation stepwithin the ledger calculationlog. For each step, the reportshows the description, ledgerinformation, output andjournal options, and gain andloss ChartKeys. (SQR)

General Ledger, ProcessMulti-Currency, Reports,Translation in Ledger

RUN_GLS5005

GLS5500ADB Definition report(average daily balancedefinition)

Prints ADB details includingdescription, purpose, andChartField information.(SQR)

General Ledger, AverageDaily Balance, ADBDefinition Report

RUN_GLS5500

GLS6000Allocation Step Report

Lists detailed information forallocation steps. (SQR)

Allocations, Reports,Allocation Step

RUN_GLS6000

GLS6002Allocation Calculation Log

Lists the allocationcalculations that wereperformed for a givenprocess step within aspecified process instance.Displays the pool, basis, andtarget amounts. (SQR)

Allocations, Reports,Allocation Calculation Logs

RUN_GLS6002





GLS6003Budget Copy CalculationLog

Lists the Budget CopyProcess calculations thatwere performed for a givenprocess step within aspecified process instance.For each process step, thereport shows the sequence,business unit, account,department, product, projectstatus, year, period, poolamount, basis amount, basistotal, target amount, andoffset amount. (SQR)

General Ledger, MaintainStandard Budgets, BudgetCopy Calculation Log

RUN_GLS6003

GLS7001Standard Journals report

Lists standard journal entriesand their status. (SQR)

General Ledger, GeneralReports, Standard Journals

RUN_GLS7001

GLS7002Ledger Activity report

Lists the beginning andending ledger balances byChartField combination andaccount. Also lists thedetailed journal line activityposted against the ledger forthe accounting periods thatare specified. (SQR)

General Ledger, GeneralReports, Ledger Activity

RUN_GLS7002

GLS7003Ledger Summary Report

Summarizes journaltotals within a ledger byChartField.

General Ledger, GeneralReports, Ledger Summary,Ledger Summary Report

RUN_GLS7003

GLS7009Posted Journal Summary

Provides the ability toreport on journals postedduring a specific run of theJournal Post process. TheJournal Post process updatesall journals posted with thevalue of the Process Instance.The Process Instance is partof the search criteria that isused by the Posted Journals -Summary report. (SQR)

General Ledger, Journals,Process Journals, PostedJournal Summary Report

RUN_GLS7009

GLS7010Ledger vs Journal Integrity

Checks for any discrepancybetween Ledger and Journaltables within a specifiedperiod range. (SQR)

General Ledger, GeneralReports, Ledger vs JournalIntegrity

RUN_GLS7010

GLS7011Journal Edit Errors

Provides detailedinformation about journaledit errors: period, journalID, date, source, referencenumber, error type, line, linedescription, field name, anderror message. (SQR)

General Ledger, Journals,Process Journals, JournalEdit Errors Report

RUN_GLS7011





GLS7012Trial Balance

Combines detail andsummary balanceinformation. Shows theending ledger balances forthe specified year and periodby ChartField combination.Also displays subtotals byChartField. Prints a finaltotal for debits and credits.(SQR)

General Ledger, GeneralReports, Trial Balance

RUN_GLS7012

GLS7015Journal Suspense Activity

Provides detailedinformation about suspendedjournals. (SQR)

General Ledger, Journals,Suspense Correction,Suspended Activity Report

RUN_GLS7015

GLS7016Ledger Activity withAttributes Report

Lists the journal activity andthe associated attributesfor one or more specificChartFields in a ledgerfor one or more periods,including beginning andending balances. (SQR)

General Ledger, GeneralReports, Ledger Activitywith Attributes, LedgerActivity with AttributesReport

RUN_GLS7016

GLS7017Ledger with Attributes

Generate a FACTS II reportfor a specific business unit,ledger, fiscal year, periodrange, adjustment periodinformation, and FACTS treegroup. You may also indicatethat the numeric field can be23 integers and 3 decimalplaces long. (SQR)

General Ledger, FederalReports, FACTS II Reports,Ledger with AttributesReport

RUN_GLS7017

GLS7500Ledger File Creation

Reads all entries on theledger and gives the endingbalance for the year andperiod by account. Output isrouted to an ASCII file in thespecified format. (SQR)

General Ledger, Ledgers,Export Ledger Data

RUN_GLS7500

GLS8012Journal Line/AccountingEntry Reconciliation

Compares journal entry lineswith accounting entries.(SQR)

General Ledger, GeneralReports, JournalLine/Acctg Reconcil(journal line/accountingreconciliation)

RUN_GLS8012

GLS8310FACTS I Validation report

This report is generatedwhen you run the FACTSI Validation process. Itdescribes any outstandingissues for each FACTS I editthat is run for your FACTS Iaccumulated data. (SQR)


RUN_CNTL_FACTSI





GLS8311FACTS I Trial Balancereport



RUN_CNTL_FACTSI

GLS8312FACTS II Trial Balance


General Ledger, FederalReports, FACTS II, FACTSII Reports, FACTS II TrialBalance

F2_RUN_GLS8312

GLS8400SF224 Transaction Report

This is a monthly reportsent to the U.S. Treasurythat identifies the dollaramounts of confirmedU.S. disbursements andcollections for an agency byAgency Location Code andfiscal month. This report isused to ensure agreementbetween the agency’srecords of disbursement andcollections and those of theU.S. Treasury. (SQR)

General Ledger, FederalReports, SF 224/ 1219/1220,SF 224 Transaction Report

RUN_GLS8400

GLS8500Federal Trial Balance report

This is a summary trialbalance report. This reportdisplays a beginningbalance, the total amount ofdebits and credits and anending balance. The data isgenerated for the specifiedChartField combination forthe fiscal year , accountingperiods, and adjustmentperiods. This report alsodisplays subtotals byChartField and grand totalsby TAS/TAFS levels. (SQR)

General Ledger, FederalReports, Federal TrialBalance

RUN_GLS8500

GLS8501Federal Transaction Register

This is an online report thatdisplays values at the fund,department, and TAS/TAFSlevels for each accountingperiod along with eachChartField’s attributes andattribute values. (SQR)

General Ledger, FederalReports, Federal TransactionRegister

RUN_GLS8501





GLS9500Fund Balance Reconciliation

This report is run afteryou run the Fund BalanceReconciliation processwhich compares accountactivity and trial balancedata imported from the U.S.Treasury contains to a federalagency’s cash activity. Itcontains any differencesbetween a federal agency’sand the U.S. Treasury’sdata. (SQR)

General Ledger, FederalReports, Fund BalanceReconciliation, GenerateReconciliation Report

RUN_FBRECON_RPT

SF224Statement of CashTransactions

SF224 is a monthly reportto the U.S. Treasury thatidentifies the dollar amountsof confirmed disbursementsand collections by TreasurySymbol, Agency LocationCode, and fiscal month. Thisreport is used by the U.S.Treasury to ensure that theagency agrees with theinternal U.S. agencies thatperform disbursementsthrough the U.S. Treasury.This option enables you tocreate a flat file of the reportto submit electronicallythrough GOALS, and to printa hard-copy of the report.

General Ledger, FederalReports, SF224 / 1219/ 1220,Run SF224 Report/CreateFile

RUN_SF224_SF1220

GLS8400SF224 Statement of CashTransaction Details

This is a monthly reportthat includes the detailtransactions that make upthe totals on the SF224- Statement of CashTransactions report.

General Ledger, FederalReports, SF224 / 1219/ 1220,SF224 Transaction Report

RUN_GLS8400





SF1219Statement of Accountability

This report is used todetermine the accountabilityof disbursing officers forfunds held outside theDepartment of Treasury(cash on hand) by U.S.Treasury Regional FinanceCenters (RFCs) and othernonmilitary agenciesthat do not do their owndisbursing. This option printsa hard-copy version ofthis report. This report isvery similar to the SF1220report. These two reports aretreated as one report whensubmitted electronically andprocessed by GOALS usingthe SF1219/1220 Createoption to create the file.


RUN_GLSF1219

SF1220Statement of TransactionsAccording toAppropriations, Funds, andReceipt Accounts report

Provides the U.S. Treasurywith a monthly statement ofpayments and collectionsperformed by agencies thatdo their own disbursing. Thisoption prints a hard-copyversion of this report. Thisreport is very similar to theSF1219 report. These tworeports are treated as onereport when submittedelectronically and processedby GOALS using theSF1219/1220 Create optionto create the file.


RUN_SF224_SF1220




CHAPTER 2

Report Samples

This chapter provides report samples.

For the online samples of these reports, see the PDF files that are published on CD-ROM with your online documentation.


Journal ID: GL84JE0104 Journal Date: 11/22/2001 Source: CFO--Chief Financial Officer Reversal: N--None Status: V--Valid

Description Benefit for allocation

1 Salaries & Wages USD 350,000.00 0.00

2 Sales Commissions & Bonuses USD 100,000.00 0.00

3 Expense Accrual USD 0.00 450,000.00

Total USD 450,000.00 450,000.00

_______________________________________________________________________________________________________________________________________________________________________________

PeopleSoft Financials

Report ID: FIN2001 JOURNAL ENTRY DETAIL REPORT Page No. 8

Run Date 12/03/2001

Run Time 10:04:30

Bus. Unit: US001--US001 NEW YORK OPERATIONS

Ledger Grp: RECORDING --Recording Ledger Group

Ledger: LOCAL --Local Currency Ledger

For the period 01/01/1900 through 12/03/2001

Source: CFO Journal ID: ALL Status: V

Line Description

Entry Event Cur Debit Credit

Journal ID: GL6_BENFT Journal Date: 01/01/1999 Source: ALO--Allocation Process Reversal: N--None Status: M--SJE Model

Description To record the Salaries, Commissions & Bonuses.

1 Salaries & Wages USD 0.00 0.00

2 Sales Commissions & Bonuses USD 0.00 0.00

3 Employee salaries payable USD 0.00 0.00

Total USD 0.00 0.00

_______________________________________________________________________________________________________________________________________________________________________________


Report ID: FIN2005 JOURNAL ENTRY WITH CHARTFIELD ATTRIBUTES REPORT Page No. 1

Run Date 11/21/2003

Run Time 11:34:07


Ledger Grp: RECORDING --Recording Ledger Group

Ledger: LOCAL --Local Currency Ledger


Source: ALL Journal ID: ALL Status: ALL

Line Description

Cur Debit Credit

PS/GL Online Entry Panel

1010 Fund Balance with Treasury F100 1 Not Distributed to GL 0.00 0.00

Distributed to GL 21,630,000.00 0.00

Not Posted to GL 0.00 0.00

Posted to GL 21,630,000.00 0.00

1020 Miscellaneous Receivables F200 1 Not Distributed to GL 0.00 0.00

Distributed to GL 0.00 9,990,000.00


Posted to GL 0.00 9,990,000.00

1110 Undeposited Collections F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 3,330,000.00 0.00

1310 Accounts Receivable F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 3,330,000.00 0.00

3100 Unexpended Appropriations F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 0.00 13,290,000.00

4115 Loan Subsidy Appropriation - D F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 9,365,000.00 0.00

4116 Entitlement Loan Subsidy Appro F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 0.00 6,065,000.00

4120 Appropriations Anticipated - I F100 1 Not Distributed to GL 0.00 0.00



Posted to GL 0.00 3,300,000.00

5200 Revenue from Services Provided F100 1 Not Distributed to GL 0.00 0.00



PeopleSoft GL

Report ID: FIN5001 GENERAL LEDGER RECONCILIATION BY SYSTEM SOURCE Page No. 1

Run Date 01/28/2003

Run Time 11:45:27

Bus. Unit: FED01--FEDERAL - BU 1

Ledger: LOCAL -- Actuals Ledger

For Fiscal Year 2002 Period 1 to 1

Account Fund Period Debit Credit

1010 Fund Balance with Treasury F100

PS/GL Online Entry Panel 1 Not Distributed to GL 0.00 0.00



Posted to GL 21,630,000.00 0.00

PS/GL Copy Journal 1 Not Distributed to GL 0.00 0.00



Posted to GL 3,300,000.00 0.00

------------------------------------------------------------------------

Total Activity: Not Distributed to GL 0.00 0.00



Posted to GL 24,930,000.00 0.00

Ledger Amount: 24,930,000.00

1020 Miscellaneous Receivables F200




Posted to GL 0.00 9,990,000.00

------------------------------------------------------------------------




Posted to GL 0.00 9,990,000.00

Ledger Amount: < 9,990,000.00>

1110 Undeposited Collections F100




Posted to GL 3,330,000.00 0.00

------------------------------------------------------------------------




Posted to GL 3,330,000.00 0.00

Ledger Amount: 3,330,000.00

1310 Accounts Receivable F100



PeopleSoft GL

Report ID: FIN5005 GENERAL LEDGER RECONCILIATION BY CHARTFIELD Page No. 1

Run Date 01/28/2003

Run Time 11:35:01




Account Fund Period Debit Credit

Report ID: PeopleSoft FinancialsGLC1000 Page No. 1

SUMMARY LEDGER DEFINITION Run Date 06.Feb.2002

Run Time 10:00:56 AM

Set ID:

Summary Ledger:

Ledger Template:

Summary Ledger ChartField Detail Ledger ChartField How Specified Tree Name Tree Level Selected Values

End of Report

Report ID: Page No. 1PeopleSoft General LedgerGLC4001

Run Date 06.Feb.2002SUMMARY CALENDARS

Run Time 5:56:35 PM

Set ID: SHARE

Summary Calendar: QT

Name: Quarterly Summary Calendar

Description: Quarterly Summary Calendar

Detail Calendar

To Be Summarized: 01

Periods in a Year: 4

-----Detail Calendar Periods--------------------------------------Summary Calendar Periods-------------------------------

Year Period Description Abbr From Period Through Period

1990 1 First Quarter Q1 1 3

1990 2 Second Quarter Q2 4 6

1990 3 Third Quarter Q3 7 9

1990 4 Fourth Quarter Q4 10 12








































COMBINATION GROUP

PeopleSoft FinancialsReport ID: Page No. 1GLC4003

Run Date 06.Feb.2002

Run Time 5:58:09 PM

Set ID: SHARE

Combination Combo CF Definition Description

Process Group:AFFILIATES Combo Group for Affiliates

Combination Group for Affiliate Codes

Anchor Values Not In Rules:

Editing Option:

Combo Group Defines:

Combo Data Table

Valid Combinations

Mark Valid

User Defined:N

Effdt From Effdt To

AFFILIATES AFFILIATE Combo Rule for Affiliates 01/01/1990 01/01/1990


Process Group:BS_EXCP Balance Sheet Exceptions

Combination Group for Balance Sheet Exceptions


Editing Option:


Combo Data Table

Invalid Combinations

Mark Valid

User Defined:N

Effdt From Effdt To

ASSET_EXCP ACCT_3COMB Asset Exception Rule 01/01/1990 01/01/1990

EQ_EXCP ACCT_3COMB Equity Exception Rule 01/01/1990 01/01/1990

LIAB_EXCP ACCT_3COMB Liability Exception Rule 01/01/1990 01/01/1990


Process Group:BSACCTS Balance Sheet Accounts

Combination Edit rule for Balance Sheet Accounts.


Editing Option:


Master Selector Tables

Valid Combinations

Mark Valid

User Defined:N

Effdt From Effdt To

ASSETS ACCT_3COMB Combo Rule for Assets Accounts 01/01/1990 01/01/1990

EQUITY ACCT_3COMB Combo Rule for Equity Accts 01/01/1990 01/01/1990

LIABILITY ACCT_3COMB Combo Rule for Liability Acct 01/01/1990 01/01/1990


Process Group:EXP-CE Expenses Combo Edit Group


Editing Option:


Combo Data Table

Invalid Combinations

Mark Valid

User Defined:N

Effdt From Effdt To

EXP-CE EXP-CE Expenses Combo Edit Rule 01/01/2000 01/01/2000


Process Group:INCSTMT Income Statement Accounts

Combination Edit rule for Revenue and Expense accounts.


Editing Option:


Master Selector Tables

Valid Combinations

Mark Valid

User Defined:N

Effdt From Effdt To

EXPENSES ACCT_3COMB Combo Rule for Expense Acct 01/01/1910 01/01/1910

REVENUE ACCT_3COMB Combo Rule Revenue Accounts 01/01/1990 01/01/1990

Report ID: Page No. 1PeopleSoft FinancialsGLC4008

Run Date 01.Nov.2001VALID JOURNAL CLASS

Run Time 6:22:47 PM

Set ID:

Budgettary onlyJournal Classt Description

SHARE

JC1 Journal Class 1 N

JC2 Journal Class 2 Y

JC3 Journal Class 3 Y

JC4 Journal Class 4 N

End of Report


Run Date 06.Feb.2002AVERAGE DAILY BALANCES PROCESSES

Run Time 8:40:40 AM

Unit:

Average Daily Balance:

Set ID:

Type:

Source/Target Ledger:

Process Date & TimeAveraged Period

Period Type:

Accounting PeriodProcess Instance

Fiscal year:

/

End of Report


Run Date 06.Feb.2002ALLOCATION GROUP DEFINITION

Run Time 5:17:26 PM

Set ID:

As Of Date:

Allocation Group:

Description:

Purpose:

Sequence Allocation Step Allocation Step Description Continue

End of Report

Crystal Report Viewer Page 1 of 1

file://C:\REPORTS\GSC7501.htm 2/21/02

Report ID: GLC7501 PeopleSoft Financials

JOURNAL ENTRY DETAIL REPORT

Unit: Ledger Group:

Journal ID: DEPR000013 Source: AM

Date: 28.Feb.2002 Reversal: None

Reversal Date:Description: Depreciation Expense

Line # RateAccount Department

Product Affiliate

Stat Statistics Amt Rate Type

RECORDIN

Project

US001

Operat Unit

ScenarioBook code

Alt Account Fund Code Program Class Budget Ref

Fund Affliate

US001

Total Lines:6

Total Base Debits: 1,208.34

1 164000 10000

EP840_1

PTP-101ADescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

2 681400 10000

EP840_1

PTP-101ADescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

3 164000 10000

EP840_1

PTP-101BDescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

4 681400 10000

EP840_1

PTP-101BDescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

5 164000 10000

EP840_1

PTP-101CDescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

6 681400 10000

EP840_1

PTP-101CDescription:

1.00000000

Reference:

CRRNTNEWYOR

K

B

End of Report

Total for Ledger S_SUM: 0

PeopleSoft GL

Report ID: GLS1001 SUMMARY LEDGER - DETAIL Page No. 1

Run Date 02/06/2002

Run Time 08:52:49


Ledger: --

As of Fiscal year 2001 from Period 1 to Period 12 ()

BalanceAccount Node DIVISION Product Area

Description: Interim Closing Ledger Template: STANDARD

Account Fieldname: ACCOUNT Interim Closing

Closing Scope: Incremental Year to Date Target Currency Option: No

Create Journal Entry: Yes , Edit JournalsJournal ID Mask: IC Journal Description: Closing Journals Journal Source: CFOJournal Doc Type: FS-CLS

Close to Multiple Retained Earnings :YesLine1 From P&L Chartfield Value Set

ACCT_INCOMESTMT To Retained Earnings Chartfield Value

ACCOUNT 360100

PL Offset Chartfield Values: Chartfield ValueACCOUNT 191000

PeopleSoft GLReport ID: GLS1002 CLOSING RULES Page No. 1

Run Date 11/13/2001Run Time 17:31:46

Set ID: SHARE--CORPORATE SETID Close Set: INTERIM As Of Date: 11/08/2001

Assets 0.00 < 2,633,800.00> 0.00 0.00 0.00

Liability 0.00 < 5,398,500.00> 0.00 0.00 0.00

Equity 0.00 0.00 0.00 0.00 0.00

Revenue 0.00 0.00 0.00 0.00 0.00

Expense 0.00 8,032,300.00 0.00 0.00 0.00

Total: 0.00 0.00 0.00 0.00 0.00

Currency: USD

PeopleSoft GL

Report ID: GLS1003 CLOSING TRIAL BALANCE Page No. 1

Run Date 11/05/2001

Run Time 18:22:36


Ledger: LOCAL -- Local Currency Ledger

Year: 1999

Account Type Beginning Balance Period Total Adjustments Closing Entry 2000 Period 0

0000005290 06/30/1999 1 USD -6,000.00 USD -6,000.00610000

0000005290 06/30/1999 4 USD 6,000.00 USD 6,000.00100108

BI00005391 07/07/2000 1 USD 18,147.00 USD 18,147.00120005

BI00005391 07/07/2000 2 USD -18,147.00 USD -18,147.00200500

BI00005391 07/07/2000 3 USD -18,147.00 USD -18,147.00403000

BI00005391 07/07/2000 4 USD 18,147.00 USD 18,147.00500000

BI00005392 08/11/2000 1 USD 1,050,000.00 USD 1,050,000.00120000

BI00005392 08/11/2000 2 USD -700,000.00 USD -700,000.00400000

BI00005392 08/11/2000 3 USD -350,000.00 USD -350,000.00

GL20000001 01/05/1999 1 USD 750,000.00 USD 750,000.00150000

GL20000001 01/05/1999 2 USD 250,000.00 USD 250,000.00151000

GL20000001 01/05/1999 3 USD 100,000.00 USD 100,000.00152000

GL20000001 01/05/1999 4 USD 250,000.00 USD 250,000.00153000

GL20000001 01/05/1999 5 USD 150,000.00 USD 150,000.00154000

GL20000001 01/05/1999 6 USD 300,000.00 USD 300,000.00155000

GL20000001 01/05/1999 7 USD 250,000.00 USD 250,000.00156000

GL20000001 01/05/1999 8 USD 500,000.00 USD 500,000.00157000

GL20000001 01/05/1999 9 USD 150,000.00 USD 150,000.00159000

GL20000001 01/05/1999 10 USD 75,000.00 USD 75,000.00160000

GL20000001 01/05/1999 11 USD -2,775,000.00 USD -2,775,000.00100002

GL20000001 01/15/1999 1 USD 1,500.00 USD 1,500.00120500

GL20000001 01/15/1999 2 USD 2,200.00 USD 2,200.00

GL20000001 01/15/1999 3 USD 1,700.00 USD 1,700.00

GL20000001 01/15/1999 4 USD 1,300.00 USD 1,300.00

GL20000001 01/15/1999 5 USD 2,500.00 USD 2,500.00

GL20000001 01/15/1999 6 USD 4,500.00 USD 4,500.00

GL20000001 01/15/1999 7 USD 1,570.00 USD 1,570.00

GL20000001 01/15/1999 8 USD 650.00 USD 650.00

GL20000001 01/15/1999 9 USD 4,525.00 USD 4,525.00

GL20000001 01/15/1999 10 USD 3,500.00 USD 3,500.00

GL20000001 01/15/1999 11 USD -23,945.00 USD -23,945.00100002

GL20000002 01/25/1999 1 USD 1,400.00 USD 1,400.00120500

GL20000002 01/25/1999 2 USD 1,500.00 USD 1,500.00

GL20000002 01/25/1999 3 USD 6,500.00 USD 6,500.00

GL20000002 01/25/1999 4 USD 7,800.00 USD 7,800.00

GL20000002 01/25/1999 5 USD 3,500.00 USD 3,500.00

GL20000002 01/25/1999 6 USD 1,250.00 USD 1,250.00

GL20000002 01/25/1999 7 USD 6,575.00 USD 6,575.00

GL20000002 01/25/1999 8 USD 965.00 USD 965.00

GL20000002 01/25/1999 9 USD 365.00 USD 365.00

GL20000002 01/25/1999 10 USD 2,540.00 USD 2,540.00

GL20000002 01/25/1999 11 USD -32,395.00 USD -32,395.00100002

PeopleSoft GL

Report ID: GLS1004 JOURNAL CLOSING STATUS Page No. 1

Run Date 11/05/2001

Run Time 17:23:22


Fiscal Year: 0

Ledger Group: RECORDING

Ledger LOCAL

Begin Date: End Date: Closing Status: Never processed by close

Journal ID Journal Dt Line Foreign Amount Base AmountAccount

Non primary ledger base currency entries in the translate ledger: None

Amounts in translate Ledger different from matching entries in primary ledger: None

Translate ledger entries with no matching entries in primary ledger:

4 USD 166.67 100001

Primary ledger entries with no matching entries in Translate ledger: None

PeopleSoft GL

Report ID: GLS1005 Page No. 1

Run Date 04/06/2001

Run Time 09:27:55


PeopleSoft GL


Run Date 04/06/2001

Run Time 09:27:55


Ledger: LED_CAD -- CAD LEDGER Base Currency: CAD

Fiscal Year 2000

PerPer Posted Total of base cur Cur Sum of Posted Base amtAccount AltAcct Operating Unit Department Prod Project ID Affl Stat

Translate ledger--POSTED_BASE_AMT do not add up to POSTED_TOTAL_AMT in base currency line: None

Non primary ledger base currency entries in the translate ledger: None

Amounts in translate Ledger different from matching entries in primary ledger: None

Translate ledger entries with no matching entries in primary ledger: None

Primary ledger entries with no matching entries in Translate ledger: None

PeopleSoft GL

Report ID: GLS1006 TRASNLATE LEDGER IN SYNC REPORT Page No. 1

Run Date 11/26/2001

Run Time 17:25:28

Bus. Unit: SPN02--SPAIN - EURO BASE CURRENCY

PeopleSoft GL

Report ID: GLS1006 TRASNLATE LEDGER IN SYNC REPORT Page No. 1

Run Date 11/26/2001

Run Time 17:25:28

Bus. Unit: SPN02--SPAIN - EURO BASE CURRENCY

Ledger: CORPORATE -- Corporate Ledger in USD Base Currency: USD

Fiscal Year 2000

PerPer Posted Total of base cur ln Sum of Posted Base amtAccount Department

Description: InterUnit - FRANCE & BLG01

Purpose: Eliminates all InterUnit transactions between FRA01, FRA03and BLG01.

Chart Keys If Set Doesn't Eliminate:

ChartField Value

If Debit: ACCOUNT 140000

If Credit: ACCOUNT 280000

Elimination Sets:

Line ChartField Value

1 ACCOUNT 100109

2 ACCOUNT 100112

3 ACCOUNT 400000

4 ACCOUNT 401000

5 ACCOUNT 402000

6 ACCOUNT 403000

7 ACCOUNT 430000

8 ACCOUNT 430100

9 ACCOUNT 500000

10 ACCOUNT 500500

11 ACCOUNT 600020

12 ACCOUNT 630000

13 ACCOUNT 631000

14 ACCOUNT 635000

15 ACCOUNT 640000

16 ACCOUNT 642000

17 ACCOUNT 643000

18 ACCOUNT 632000

19 ACCOUNT 100119

PeopleSoft GLReport ID: GLS2000 ELIMINATION SET DEFINITION Page No. 1

Run Date 11/06/2001Run Time 15:18:40

Set ID: CONSL--For Consolidation Processing As Of Date: 10/31/2001

Elimination Set: EL-FRA/BLG

Description: Default Minority Interest Set

Match Affiliate Value: Yes

SetID Chartfield Value Set Chartfield Tree Name/Level Nodes/Values

Parent Investment: SHARE ACCT_PARENT_INVEST ACCOUNT ACCTROLLUPDetail - Selected Parents INVESTMENT

Subsidiary Equity: SHARE ACCT_EQUITY ACCOUNT ACCTROLLUPDetail - Selected Parents EQUITY

Parent Minority Interest Liability: ACCOUNT 313000

Out of Balance Chartfield Value, if Debit: ACCOUNT 140000

Out of Balance Chartfield Value, if Credit: ACCOUNT 280000

PeopleSoft GLReport ID: GLS2001 MINORITY INTEREST SET DEFINITION Page No. 1

Run Date 11/06/2001Run Time 15:19:27


Minority Interest Set: DEFAULT

Description: Consolidation in Euros

Business Unit:

Eliminations Journals:Journal ID Mask: CSL-EUSource: CONGroup By ChrtFld for Out of Bal Amt: BUSINESS_UNIT Elimination Reversal: Beginning of Next Period

ChartFields Included in Eliminations: ACCOUNT AFFILIATE DEPTID

All Elimination Sets Apply: No

Elimination Sets: ELIM-ALL InterUnit Eliminations All BUs

Default Minority Interest Set: DEFAULT Default Minority Interest Set

Minority Interest Set Override:SUB-BLG01 DEFAULT

PeopleSoft GLReport ID: GLS2002 CONSOLIDATION DEFINITION Page No. 1

Run Date 11/27/2001Run Time 17:53:04

Set ID: CONSL--For Consolidation Processing Consol Set: EURO_CONSLAs Of Date: 11/26/2001

PeopleSoft GL

Report ID: GLS2003 CONSOLIDATION OUT OF BALANCE REPORT Page No. 1

Run Date 02/06/2002

Run Time 10:27:20

Set ID: US001--

Consol Set: %

As Of Date: 01/31/2002

Tree Name: %

Unit Ledger Elim Set Debit Credit Balance

PeopleSoft GL

Report ID: GLS2004 MINORITY INTEREST ELIMINATIONS & ADJUSTMENTS Page No. 1

Run Date 02/06/2002

Run Time 10:28:08

Set ID: US001--

Tree Name: %

Consol Set: %

As Of Date: 01/31/2002

Minority Interest Set:

Subsidiary Entity:

Unit Ledger Account Description Node Name Debit Credit Balance

Dup Elimin.Set Line ACCOUNT

ELIM-ALL 59 627006 XELIM-ALL 60 627006 X

ELIM-ALL 85 701000 XELIM-ALL 86 701000 X

4 duplicated Elimination Lines found.

PeopleSoft GLReport ID: GLS2005 ELIMINATION SETS AUDIT Page No. 1

Run Date 11/06/2001Run Time 15:31:22

Set ID: CONSL--For Consolidation Processing Consol Set: EURO_CONSLAs Of Date: 10/31/2001

Description: Equitization of Net Income

Purpose: This rule will create equitization journals based on the netincome of the Subsidiaries

Create Elimination: Yes

SetID Chartfield Value Set Chartfield Tree Name/Level Values/Nodes

Subsidiary Source SHARE ACCT_INCOMESTMT ACCOUNT ACCTROLLUP/RPT_TYPEDetail - Selected Parents INCSTMT

Chartfield ValueParent Target Investment ACCOUNT 170000 Investment in Subsidiaries

Investment Offset ACCOUNT 360100 Retained Earnings - Division A

Minority Interest Expense ACCOUNT 695000 Minority Interest Expense

Liability ACCOUNT 313000 Minority Interest

Subsidiary Offset Offset ACCOUNT 830001 Income Offset

Summary ACCOUNT 835001 Income Summary

PeopleSoft GLReport ID: GLS2006 EQUITIZATION RULE DEFINITION Page No. 1

Run Date 11/06/2001Run Time 15:19:18


Equitization Rule: NETINCOME

SUB-AUS01 A 01/01/1999 Ownership of AUS01 BUSINESS_UNIT AUS01 JPN01 90.0000000000 Y N

PeopleSoft GL

Report ID: GLS2007 CONSOLIDATION OWNERSHIP Page No. 1

Run Date 11/06/2001

Run Time 15:19:47

Set ID: CONSL--For Consolidation Processing

As Of Date: 10/31/2001

Ownership Set Status Effective Date Description Entity Chartfield Subsidiary Entity Parent Ownership % Controlling Equitize

SUB-US005 US005 LOCAL NETINCOME < 10,000.00> 170000

90.000000000 < 9,000.00> USD US001 LOCAL

----------------------- -----------------------

< 10,000.00> < 9,000.00>

PeopleSoft GL

Report ID: GLS2008 EQUITIZATION CALCULATION LOG Page No. 1

Run Date 11/09/2001

Run Time 15:48:52

Equitization Group: ALLRULES

Tree Name: CONSOLIDATE_CORP

As Of Date: 11/09/2001 Process Instance: 69

--------------------------------- From ----------------------------------- ------------------------- To --------------------------------

Ownership Sub Entity Ledger Eqtz Rule Source Amount Account

Department Percent Target Amount Target Ledger

End of Report

Currency: Account Oper Unit Fund

USD 120500 Employee Advances

O EmployeeID

IXHEEE101

01/15/1999 GL20000001 0 1 1,500.00

----------------------

Open Item Key Total: 1,500.00

IXHEEE102 01/15/1999 GL20000001 0 2 2,200.00

----------------------


IXHEEE103 01/15/1999 GL20000001 0 3 1,700.00

----------------------


IXHEEE104 01/15/1999 GL20000001 0 4 1,300.00

----------------------


IXHEEE105 01/15/1999 GL20000001 0 5 2,500.00

----------------------


IXHEEE106 01/15/1999 GL20000001 0 6 4,500.00

----------------------


IXHEEE107 01/15/1999 GL20000001 0 7 1,570.00

----------------------


IXHEEE108 01/15/1999 GL20000001 0 8 650.00

----------------------

Open Item Key Total: 650.00

IXHEEE109 01/15/1999 GL20000001 0 9 4,525.00

----------------------


IXHEEE110 01/15/1999 GL20000001 0 10 3,500.00

----------------------

PeopleSoft GL

Report ID: GLS3000 OPEN ITEMS Page No. 1

Run Date 11/05/2001

Run Time 18:53:58


PeopleSoft GL

Report ID: GLS3000 OPEN ITEMS Page No. 1

Run Date 11/05/2001

Run Time 18:53:58



Currency: USD Account: ALL Oper Unit: ALL Fund: ALL

Open Item Key Opened Journal Seq Line Amount

Primary BU(debit) vs. Balance BU(credit):

BUSINESS UNIT US001

ACCOUNT 100105

AFFILIATE US003

----------------------------- ----------------------------- -----------------------------

Balance Posted Total 0 360,800.00 USD 360800.00 USD

Balance Posted Base 0.000 360,800.000 USD

============================= ============================= =============================

PeopleSoft GL

Report ID: GLS3001 INTERUNIT RECONCILIATION Page No. 1

Run Date 11/06/2001

Run Time 16:36:36

Bus. Unit: US003--US003 CALIFORNIA OPERATIONS

PeopleSoft GL

Report ID: GLS3001 INTERUNIT RECONCILIATION Page No. 1

Run Date 11/06/2001

Run Time 16:36:36

Bus. Unit: US003--US003 CALIFORNIA OPERATIONS


Year: 1999

Period: 12

Currency: USD

Balance w/: ALL

Sort by: Sort by Business Unit

ChartField Primary Values Balancing Values Variance

----------------------------- ----------------------------- ----------------------------- -----------------------------

DAILY Daily Batch Run D--Daily Monday

Tuesday

Wednesday

Thursday

Friday

PeopleSoft GL


Run Date 11/05/2001

Run Time 18:55:16

Set ID: SHARE--CORPORATE SETID

As Of Date: 11/05/2001

Schedule: DAILY%

Day of Day of --------------- User Defined Events ---------------

Schedule: Description Frequency the Week Month the Month Occ Date Time Description

Description: Combo Rule for Assets Accounts Effective Date From: 01/01/1990 To: 01/01/2099

Combo CF Definition: ACCT_3COMB

ChartFiel How Specified Set Tree Name Tree Level Selected Value

ACCOUNT Selected Tree Nodes SHAR A

CASH

PREPAIDS

RECEIVABLES

DEPTID Selected Tree Nodes SHAR D

NO_DEPTID

PRODUCT Selected Tree Nodes SHAR P

NO_PRODUCT

ACCOUNT Selected Tree Nodes SHAR A

INVESTMENT

DEPTID Selected Tree Nodes SHAR D

FIN_GRP

PRODUCT Selected Tree Nodes SHAR P

NO_PRODUCT


Report ID: GLS4002 CHARTFIELD COMBINATION RULES Page No. 1

Run Date 11/05/2001

Run Time 18:59:17


As Of Date: 10/30/2001

Combination Rule: ASSETS

Description: Translation

Purpose: Translated ledgers from base currency or specified currency to Translate Ledger Group

From Ledger Group: RECORDING

From Ledger: LOCAL From Currency: Base Currency

Target Ledger Group: TRANSLATE

Target Ledger: TRANSLATE

Journal Id Mask: TRNS Source: MCP

Mark for Post: Yes

Translation Reversal: Beginning of Next Period Output Option: Create Journals

Target ChartFields: ACCOUNT

Gain ChartFields: ACCOUNT 315000

Loss ChartFields: ACCOUNT 315000

Rule Description TimeSpan Rate ChartField How Specified Tree Name Level Select Value

Rule Description TimeSpan Rate ChartField How Specified Tree Name Level Select Value

ASLI_CRRNT Assets/Liab at Current Rate BAL CRRNT ACCOUNT Selected Tree Nodes ACCTROLLUP ASSETS

LIABILITIES

EQ_HIST1A Capital Stock at Historical BAL HST1A ACCOUNT Selected Detail Values 340000

REVEXP_AVG Revenue & Expense at Average YTD AVG ACCOUNT Selected Tree Nodes ACCTROLLUP EXPENSES

REVENUES

RE_HISTRE Retained Earnings at HistRE BAL HSTRE ACCOUNT Selected Tree Nodes ACCTROLLUP RETEARN

PeopleSoft GL

Report ID: GLS5000 CURRENCY TRANSLATION DEFINITION Page No. 1

Run Date 11/05/2001

Run Time 19:00:11


As Of Date: 10/31/2001

Translation Step: TRNS_MB

Description: Revalue Multibook Purpose: Revalue Multibook

From Ledger Group: RECORDING Ledger: LOCAL

TimeSpan: BAL Exchange Rate Type: CRRNT

Journal Id Mask: REVALMSource: CFO Mark for Post: No

Revaluation Reversal: Beginning of Next Period Output Option: Create Journals

Target ChartFields: ACCOUNT ALTACCT

Gain ChartFields: ACCOUNT 692000

Loss ChartFields: ACCOUNT 692201

ChartField How Specified Tree Name Level Select Value

ACCOUNT Selected Tree Nodes ACCTROLLUP ALLACCOUNTS

PeopleSoft GLReport ID: GLS5001 CURRENCY REVALUATION DEFINITION Page No. 1

Run Date 11/05/2001Run Time 19:01:13

Set ID: SHARE--CORPORATE SETID As Of Date: 10/31/2001

Revaluation Step: MULTIBOOK

200000 BEF 2000 6 36.87371881 -324,866 -8,810.23

206100 BEF 2000 6 36.87371881 21,000 569.51

500000 13000 BEF 2000 6 36.87371881 97,656 2,648.39

600020 14000 BEF 2000 6 36.87371881 103,320 2,802.00

621000 10500 BEF 2000 6 36.87371881 2,890 78.38

641000 10500 BEF 2000 6 36.87371881 100,000 2,711.96

------------------------------------

Translation Gain or Loss Adjustment:

316000 -0.01

PeopleSoft GL

Report ID: GLS5002 TRANSLATION CALCULATION LOG Page No. 1

Run Date 08/16/2000

Run Time 15:15:43

Process Instances: 0000003916 to 0000003916

Translation Step: BEF_USD%

Process Instance: 0000003916 Translation Step: BEF_USD Business Unit: BLG01 Target Ledger: ALLOC-USD Target Currency: USD

Account Dept Product Project ID Currency Year Per Exchange Rate Posted Total Amount Translated Amount

400000 DEM 85.07181094 -6,530.00 -555,519 -555,519 0

400000 JPY 203.55009509 -6,930 -11,920 -14,106 -2,186

400000 USD 168.20773009 -100,000.00 -15,330,452 -16,820,773 -1,490,321

500000 USD 168.20773009 25,000.00 4,027,937 4,205,193 177,256

620000 USD 168.20773009 100,000.00 15,330,452 16,820,773 1,490,321

621000 JPY 203.55009509 6,930 11,920 14,106 2,186

631000 DEM 85.07181094 6,530.00 555,519 555,519 0

------------------------------------

Revaluation Gain or Loss Adjustment:

768000 USD -177,256

PeopleSoft GL

Report ID: GLS5003 REVALUATION CALCULATION LOG Page No. 1

Run Date 08/17/2000

Run Time 13:23:01

GLS5003


Revaluation Step: REVALBANK%

Process Instance: 0000000115 Revaluation Step: REVALBANK Business Unit: SPN01 Ledger: LOCAL Base Currency: ESP

Account Dept Product Project ID Currency Exchange Rate Posted Total Amount Posted Base Amount Revaluated Amount Adjustment Amount

100001 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100002 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100003 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100004 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100006 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100007 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100008 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100009 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100010 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100011 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100012 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100013 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100015 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100016 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

100017 USD 1.25300139 1,000.00 1,250.00 1,253.00 3.00

------------------------------------

Adjustment:

315000 USD -45.00

PeopleSoft GL

Report ID: GLS5004 TRANS W/IN LEDG CALCULATION LOG Page No. 1

Run Date 09/08/2000

Run Time 18:16:02

GLS5004


Translation Step: TWIN_RECT%

Process Instance: 0000000034 Translation Step: TWIN_RECT Business Unit: KUS02 Ledger: LED_CAD Base Currency: CAD

Account Dept Product Project ID Currency Exchange Rate Posted Total Amount Posted Base Amount Amount Adjustment Amount

PeopleSoft GLReport ID: GLS5005 TRANS W/IN LEDG DEFINITION Page No. 1

Run Date 02/06/2002Run Time 16:40:17

Set ID: SHARE--CORPORATE SETID As Of Date: 01/31/2002

Translation Step:

ChartField How Specified Tree Name Level Select Value

ADB Type Display Management

Description: Local Month to Date Averages

Purpose: Local Month to Date Averages

Ledger: LOCAL

ADB Amount Record: LEDGER_ADB_MTD

Work Table Record: ADB_WTA_TAO

ADB Amount Field: POSTED_TRAN_AMT

Target Amount Field POSTED_TRAN_AMT

Target End Balance Field POSTED_TRAN_EBAL

Target Aggregate Amount Field POSTED_TRAN_AGGR

ADB Amount Field2: POSTED_TOTAL_AMT

Target Amount Field POSTED_TOTAL_AMT

Target End Balance Field POSTED_TOTAL_EBAL

Target Aggregate Amount Field POSTED_TOTAL_AGGR

ADB Amount Field2: POSTED_BASE_AMT

Target Amount Field POSTED_BASE_AMT

Target End Balance Field POSTED_BASE_EBAL

Target Aggregate Amount Field POSTED_BASE_AGGR

No Adjustment Period

Balanced ADB: No

ADB ChartField Ledger ChartField How Specified Tree Name Tree Level Select Value

ACCOUNT ACCOUNT Detail - Selected Parents ACCTROLLUP BALSHEET

CURRENCY_CD CURRENCY_CD Selected Detail Values USD

PeopleSoft GLReport ID: GLS5500 AVERAGE DAILY BALANCE DEFINITION Page No. 1

Run Date 11/05/2001Run Time 19:08:22


Average Daily Balance: LOCALMTD

Effective Date: 01-JAN-1900 Description: GL to PC Rent Allocation

Allocation Type: Prorata with Record Basis

Pool: RECORDING Ledger Pool TimeSpan: PER Pool Factor %: 100 Zero Pool: Select Next Pool

Basis: PROJ_RES_CAL_VW Table Basis TimeSpan: PER Basis Factor %: 100 Zero Basis: Stop Processing

Target: PROJ_RESOURCE Table Target TimeSpan: PER Document Type:

Bypass VAT Yes No Journals: Issue Error Message

Table Output: Update Existing Amounts

Distribute Cents: First Target Line Round Option: Normal

Calculation Log: PC_ALLOC_CALC Basis Work Table: ALC_PC_B_TAO Jrnl Work Table: ALC_PC_T_TAO

Amount Fields: Pool & Pool Base Curr & Pool Transaction Amo Fixed Pool Amount Basis &

Target & Target Base Curr & Target Transaction Amo Offset Offset Base Curr Offset Transaction Amount

Calc Log Pool Calc Log Pool BC Log Pool Transaction Calc Log Basis Calc Log Basis Total

Calc Log Target Calc Log Target BC Log Target Transaction

POSTED_TOTAL_AMT POSTED_BASE_AMT 0 FOREIGN_AMOUNT

FOREIGN_AMOUNT RESOURCE_AMOUNT

Record Field Charge From Source How Field Specified Tree Name Level Selected Value or Tree Node Fix Basis

POOL ACCOUNT Selected Detail Values 640000

DEPTID Selected Detail Values 41000

LEDGER Selected Detail Values LOCAL

BASIS ACTIVITY_ID Selected Detail Values CUSTOMIZE

EVALUATE

INSTALL

ANALYSIS_TYPE Selected Detail Values ACT

BUSINESS_UNIT Selected Detail Values US004

PeopleSoft GL

Report ID: GLS6000 ALLOCATION STEP DEFINITION Page No. 1

Run Date 11/21/2003

Run Time 12:47:10


As Of Date: 11/21/2003

Allocation Step: GL_TO_PC

US004 2002 2 0 0.00 0 JPY

0.00 0.00 USD_______________________________________________________________________________________________________________________________________________________________________________

US004 2002 2 0 0.00 0 JPY

0.00 0.00 USD_______________________________________________________________________________________________________________________________________________________________________________

Total 0 JPY

0 JPY

PeopleSoft GL

Report ID: GLS6002 ALLOCATIONS CALCULATION LOG Page No. 1

Run Date 02/06/2002

Run Time 13:38:53

GLS6002


Allocation Step: %

Process Instance: 0000000663 Allocation Step: PCTOPC003

Basis Amount Target Amount

Unit Year Per Pool Amount Basis Total Target Base Curr AmtAccount

US001 100002 1999 1 -153,525.00 -153,525.00 USD -153,525.00 USD

US001 100002 1999 1 -6,440,000.00 -6,440,000.00 USD -6,440,000.00 USD

US001 100105 1999 1 360,800.00 360,800.00 USD 360,800.00 USD

US001 100106 1999 1 240,600.00 240,600.00 USD 240,600.00 USD

US001 100107 1999 1 228,050.00 228,050.00 USD 228,050.00 USD

US001 100108 1999 1 195,750.00 195,750.00 USD 195,750.00 USD

US001 120500 1999 1 153,525.00 153,525.00 USD 153,525.00 USD

US001 150000 1999 1 750,000.00 750,000.00 USD 750,000.00 USD

US001 151000 1999 1 250,000.00 250,000.00 USD 250,000.00 USD

US001 152000 1999 1 100,000.00 100,000.00 USD 100,000.00 USD

US001 153000 10000 1999 1 250,000.00 250,000.00 USD 250,000.00 USD

US001 154000 1999 1 150,000.00 150,000.00 USD 150,000.00 USD

US001 155000 1999 1 300,000.00 300,000.00 USD 300,000.00 USD

US001 156000 1999 1 250,000.00 250,000.00 USD 250,000.00 USD

US001 157000 1999 1 500,000.00 500,000.00 USD 500,000.00 USD

US001 159000 1999 1 150,000.00 150,000.00 USD 150,000.00 USD

US001 160000 1999 1 75,000.00 75,000.00 USD 75,000.00 USD

US001 201500 14000 1999 1 -450,000.00 -450,000.00 USD -450,000.00 USD

US001 207000 14000 1999 1 -172,500.00 -172,500.00 USD -172,500.00 USD

US001 207000 20000 1999 1 -125,000.00 -125,000.00 USD -125,000.00 USD

US001 207000 25000 1999 1 -250,000.00 -250,000.00 USD -250,000.00 USD

US001 212000 14000 1999 1 -15,000.00 -15,000.00 USD -15,000.00 USD

US001 215000 1999 1 -38,000.00 -38,000.00 USD -38,000.00 USD

US001 600010 1999 1 750,000.00 750,000.00 USD 750,000.00 USD

US001 600020 1999 1 250,000.00 250,000.00 USD 250,000.00 USD

US001 610000 1999 1 350,000.00 350,000.00 USD 350,000.00 USD

US001 610000 10000 1999 1 500,000.00 500,000.00 USD 500,000.00 USD

US001 614000 1999 1 100,000.00 100,000.00 USD 100,000.00 USD

US001 614000 1999 1 250,000.00 250,000.00 USD 250,000.00 USD

US001 615000 1999 1 50,000.00 50,000.00 USD 50,000.00 USD

US001 616000 1999 1 25,000.00 25,000.00 USD 25,000.00 USD

US001 616100 1999 1 15,000.00 15,000.00 USD 15,000.00 USD

US001 616200 1999 1 10,000.00 10,000.00 USD 10,000.00 USD

US001 617000 1999 1 300,000.00 300,000.00 USD 300,000.00 USD

US001 620000 20000 1999 1 25,000.00 25,000.00 USD 25,000.00 USD

US001 620000 22000 SERVRS 1999 1 75,000.00 75,000.00 USD 75,000.00 USD

US001 620000 25000 1999 1 50,000.00 50,000.00 USD 50,000.00 USD

US001 621000 20000 1999 1 25,000.00 25,000.00 USD 25,000.00 USD

US001 621000 25000 1999 1 50,000.00 50,000.00 USD 50,000.00 USD

US001 621100 20000 1999 1 50,000.00 50,000.00 USD 50,000.00 USD

US001 621100 25000 1999 1 100,000.00 100,000.00 USD 100,000.00 USD

US001 621200 20000 1999 1 25,000.00 25,000.00 USD 25,000.00 USD

US001 621200 25000 1999 1 50,000.00 50,000.00 USD 50,000.00 USD

US001 630000 1999 1 10,000.00 10,000.00 USD 10,000.00 USD

US001 631000 1999 1 9,000.00 9,000.00 USD 9,000.00 USD

PeopleSoft GL

Report ID: GLS6003 BUDGET COPY CALCULATION LOG Page No. 1

Run Date 11/09/2000

19:42:24

GLS6003


Budget Copy Step: TEST%

Process Instance: 0000000206 Budget Copy Step: TEST

Unit Account Dept Product Project ID Scenario Stat Per Pool Amount Target Amount Target Base Curr Amt

_______________________________________________________________________________________________________________________________________________________________________________

_______________________________________________________________________________________________________________________________________________________________________________SJE ID: GL_BENFIT Salaries, Comm & Bonus

SJE Detail 1 - Salaries, Comm & Bonus

Status : Completed Type: Template

Model Journal: GL6_BENFT Date: 01/01/1999 Unpost: 0

Standard Journal: GL_BENFIT1 Allow Change: Yes

Scheduled: Creation Lead Days: 365

Journals Created

Date Ledger Group Unpost Status Source Lns Total Debits Total Credits

01/25/1999 RECORDING 0 Posted ALO 3 450,000.00 450,000.00




05/25/1999 RECORDING 0 Valid ALO 3 500,000.00 500,000.00




09/25/1999 RECORDING 0 Edit Req'd ALO 3 525,000.00 525,000.00



_______________________________________________________________________________________________________________________________________________________________________________

PeopleSoft GL

Report ID: GLS7001 STANDARD JOURNAL ENTRIES STATUS Page No. 1

Run Date 11/28/2001

Run Time 17:59:51



SJE ID: GL_BENFIT%

Journal ID: GL_BENFIT1

100002 USD Beginning Balance: 0.00

Total Activity: < 6,593,525.00>

Ending Balance: < 6,593,525.00>

_________________________________________________________________________________________________________________________________________________________________________________


Total Activity: 360,800.00

Ending Balance: 360,800.00

_________________________________________________________________________________________________________________________________________________________________________________




_________________________________________________________________________________________________________________________________________________________________________________




_________________________________________________________________________________________________________________________________________________________________________________




_________________________________________________________________________________________________________________________________________________________________________________




_________________________________________________________________________________________________________________________________________________________________________________




_________________________________________________________________________________________________________________________________________________________________________________




PeopleSoft GL

Report ID: GLS7002 GENERAL LEDGER ACTIVITY Page No. 1

Run Date 11/09/2001

Run Time 15:12:37


PeopleSoft GL


Run Date 11/09/2001

Run Time 15:12:37




Account: Department: Currency Code: USD

Account DepartmentCur Journal Date Journal ID Seq Line Account Department Debit Credit Balance

115100 ST Investments under 1 Yr USD

12/27/2001 MKDEC1 1 USD 2,559,900.00 0.00 115100 ST Investments under 1 Yr USD

Beginning Balance: 0.00 Total Activity: 2,559,900.00 Ending Balance: 2,559,900.00

________________________________________________________________________________________________________________________________________________________________________________ 122000 Prepaid Expenses USD

12/27/2001 MKDEC1 2 USD 410,763.11 0.00 122000 Prepaid Expenses USD

Beginning Balance: 0.00 Total Activity: 410,763.11 Ending Balance: 410,763.11

________________________________________________________________________________________________________________________________________________________________________________ 124000 Accrued Facility Fees USD

12/27/2001 MKDEC1 3 USD 30,459.55 0.00 124000 Accrued Facility Fees USD

Beginning Balance: 0.00 Total Activity: 30,459.55 Ending Balance: 30,459.55

________________________________________________________________________________________________________________________________________________________________________________ 130000 Receiving/Inspection Inventory USD

12/27/2001 MKDEC1 4 USD 1,100,422.89 0.00 130000 Receiving/Inspection Inventory USD

Beginning Balance: 0.00 Total Activity: 1,100,422.89 Ending Balance: 1,100,422.89

________________________________________________________________________________________________________________________________________________________________________________

PeopleSoft GLReport ID: GLS7003 Page No. 1

Run Date 10/01/2003Run Time 18:51:51


PeopleSoft GLReport ID: GLS7003 Page No. 1

Run Date 10/01/2003Run Time 18:51:51

Bus. Unit: US001--US001 NEW YORK OPERATIONS Ledger: LOCAL -- Local Currency Ledger For Fiscal Year 2001 Period 1 To 12Currency Code USD

Account Journal Date Journal ID Seq Line Debit Credit Balance Currency

6 0000005290 06/30/1999 CFO To reclass Salaries 2 6,000.00 6,000.00USD 0.00

Period 6 Total 2 6,000.00 6,000.00USD

PeopleSoft GL

Report ID: GLS7009 POSTED JOURNAL SUMMARY BY JOURNAL ID FOR PROCESS INSTANCE 427 Page No. 1

Run Date 11/05/2001

Run Time 19:28:23


Ledger Grp: RECORDING -- Local Currency Ledger


Fiscal Year:1999

Period Journal ID Jrnl Date Src Descr Lines Debit Credit Stat Amount

End of Report

No discrepancy found for Periods 1 thru 12

PeopleSoft GL

Report ID: GLS7010 LEDGER VS. JOURNAL INTEGRITY REPORT Page No. 1

Run Date 12/13/2001

Run Time 14:34:43



Fiscal Year:2001

Period Journal Amount Ledger Amount Difference StatOper Unit

Fund

Program

Class

End of Report

1 GL20000014 01/05/1999 ONL HEADER JRNL_HDR_STATUS Journal is not balanced on journal totals or balancing

chartfield totals. (5860/48)

PeopleSoft GL

Report ID: GLS7011 JOURNAL EDIT ERRORS Page No. 1

Run Date 12/19/2001

Run Time 09:46:22


Ledger Grp: RECORDING -- Recording Ledger Group

Fiscal Year:1999

Request 1--test

Source:ALL Journal ID:ALL Journal Date:ALL

Business Unit IU:US001

Pd Journal_ID Jrnl Date Src Ref No. Error Type Line Line Description Field Name Entry Event Error message

100002 USBNK - Disbursements Account 0.00 6,593,525.00

100105 Due From - US003 360,800.00 0.00

100106 Due From - US004 240,600.00 0.00

100107 Due From - US005 228,050.00 0.00

100108 Due From - US006 201,750.00 0.00

120500 Employee Advances 153,525.00 0.00

150000 Land 750,000.00 0.00

151000 Buildings and Improvements 250,000.00 0.00

152000 Leasehold Improvements 100,000.00 0.00

153000 Furniture and Fixtures 250,000.00 0.00

154000 Machinery and Equip 150,000.00 0.00

155000 Automobiles 300,000.00 0.00

156000 Computer Hardware 250,000.00 0.00

157000 Construction in Progress 500,000.00 0.00

159000 Lease Equip 150,000.00 0.00

160000 Other Assets 75,000.00 0.00

201500 Employee salaries payable 0.00 2,350,000.00

207000 Expense Accrual 0.00 2,783,500.00

212000 Accrued Liability 0.00 75,000.00

215000 Lease Liab 0.00 190,000.00

600010 Sales Tax 750,000.00 0.00

600020 Consulting Services 250,000.00 0.00

PeopleSoft GL

Report ID: GLS7012 TRIAL BALANCE Page No. 1

Run Date 11/06/2001

Run Time 17:36:02



As of Year 1999 and Period 6

Base Currency: USD

Transaction Debit Transaction CreditAccount

CORPORATE TRANS01 TRANS01 01/05/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 10,500.000> USD_______________________________________________________________________________________________________________________________________________________________________________

EURO TRANS01 01/05/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 9,674.480> EUR_______________________________________________________________________________________________________________________________________________________________________________

LOCAL TRANS01 01/05/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 390,266.000> BEF_______________________________________________________________________________________________________________________________________________________________________________

CORPORATE TRANS07 TRANS07 01/05/2000 4 Balance Suspense 4 SBS 899998 < 5,250.000> CAD

< 4,189.940> USD_______________________________________________________________________________________________________________________________________________________________________________

EURO TRANS07 01/05/2000 4 Balance Suspense 4 SBS 899998 < 5,250.000> CAD

< 3,860.520> EUR_______________________________________________________________________________________________________________________________________________________________________________

LOCAL TRANS07 01/05/2000 4 Balance Suspense 4 SBS 899998 < 5,250.000> CAD

< 155,733.000> BEF_______________________________________________________________________________________________________________________________________________________________________________

CORPORATE TRANS08 TRANS08 01/05/2000 4 Balance Suspense 4 SBS 899998 < 94,500.000> BEF

< 2,542.490> USD_______________________________________________________________________________________________________________________________________________________________________________

EURO TRANS08 01/05/2000 4 Balance Suspense 4 SBS 899998 < 94,500.000> BEF

< 2,342.590> EUR_______________________________________________________________________________________________________________________________________________________________________________

LOCAL TRANS08 01/05/2000 4 Balance Suspense 4 SBS 899998 < 94,500.000> BEF

< 94,500.000> BEF_______________________________________________________________________________________________________________________________________________________________________________

CORPORATE TRANS09 TRANS09 02/01/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 10,500.000> USD_______________________________________________________________________________________________________________________________________________________________________________

EURO TRANS09 02/01/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 9,674.480> EUR_______________________________________________________________________________________________________________________________________________________________________________

LOCAL TRANS09 02/01/2000 5 Balance Suspense 5 SBS 899998 < 10,500.000> USD

< 390,266.000> BEF_______________________________________________________________________________________________________________________________________________________________________________

PeopleSoft GL

Report ID: GLS7015 SUSPENDED ACTIVITY Page No. 1

Run Date 11/06/2001

Run Time 17:38:41

Bus. Unit: BLG01--BELGIUM OPERATIONS

Ledger Grp: RECORDING -- Recording Ledger Group

Journal ID: ALL Journal Date: ALL

Foreign Amount

Ledger Journal ID Journal Date Line Line DescriptionSusp Line Source Account Monetary Amount

USD Beginning Balance: 0.00

Total Activity: 0.00

Ending Balance: 0.00

_________________________________________________________________________________________________________________________________________________________________________________

PeopleSoft GL


Run Date 10/01/2003

Run Time 20:49:30


PeopleSoft GL


Run Date 10/01/2003

Run Time 20:49:30




Currency Code: USD

Cur Journal Date Journal ID Seq Line Debit Credit Balance

1010 Fund Balance with Treasury Beginning Balance: 0.00 B D D

Total Activity: 20,000,000.00Ending Balance: 20,000,000.00

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1010 Fund Balance with Treasury Beginning Balance: 0.00 B D F

D 06 0100 Total Activity: 0.00Ending Balance: 0.00

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 3101 Unexpended Appropriations- Rec Beginning Balance: 0.00 B D

D Total Activity: (20,000,000.00)Ending Balance: (20,000,000.00)

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 3103 Unexpended Appriations-Trans-O Beginning Balance: 0.00 B D F


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4119 Other Appropriations Realized Beginning Balance: 0.00 P D 107-1 B D

D X Total Activity: 20,000,000.00Ending Balance: 20,000,000.00

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4175 Allocation Transfers of Curren Beginning Balance: 0.00 P 107-2 B D F


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 4450 Unapportioned Authority Beginning Balance: 0.00 B D

D Total Activity: 0.00Ending Balance: 0.00

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PeopleSoft GLReport ID: GLS7017 GENERAL LEDGER ACTIVITY WITH FUND AND ACCOUNT ATTRIBUTES Page No. 1

Run Date 10/01/2002Run Time 10:58:49

Bus. Unit: FED01--IT Services Agency

PeopleSoft GLReport ID: GLS7017 GENERAL LEDGER ACTIVITY WITH FUND AND ACCOUNT ATTRIBUTES Page No. 1

Run Date 10/01/2002Run Time 10:58:49

Bus. Unit: FED01--IT Services Agency Ledger: LOCAL -- Actuals Ledger Summary VersionFor Fiscal Year 2002 Period 1 to 1Fund: 0105X Currency Code: USD

AUT DEF PLaw CAT CBS RIF AVT TRPAcct Description Cohort Yr Balance BOR BEA YRB TAG TAC ADF FUN---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

No differences found.

PeopleSoft GLReport ID: GLS8012 JOURNAL LINE/ACCOUNTING ENTRY RECONCILIATION REPORT Page No. 1

Run Date 02/06/2002Run Time 17:44:37

Bus. Unit: --US001 NEW YORK OPERATIONSLedger: -- Local Currency Ledger2001 From Period 1 To 12

BudgetJournal ID Journal Date Account AP FY Acctg Defn Jrnl Status Journal Amt Acctg Line Amt Difference

End of Report

Validation Status: PASS - All accounts have valid RT7 values.

--- Accounting Edit 1 - This edit will check that the sum of the ending balances for all appropriate SGL accounts is equal to zero.

Fund Acct SGL Acct Fund Grp TAgcy TAcct TRP CatB Pgm CYR Debit Balance Credit Balance

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------0105X 4119 4119 0105 20,000,000.000105X 4175 4175 0105 06 0100 (500,000.00)0105X 4450 4450 0105 0105X 4510A1 4510 0105 0105X 4610 4610 0105 (19,500,000.00)

-------------------------------------Totals: 20,000,000.00 (20,000,000.00)

Validation Status: PASS - The sum of the budgetary account DR balances EQUAL the sum of the budgetary account CR balances.

--- Accounting Edit 2 - This edit will be Valid when the Sum of the ST account balances equals the Sum of the TO balances. (Lines 7 and 11 from the SF133)

Fund Acct SGL Acct Fund Grp TAgcy TAcct TRP CatB Pgm CYR Attribute Begin Balance PTD Balance ST Amount TO Amount

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------0105X 4119 4119 0105 TO_ENDING 0.00 20,000,000.00 20,000,000.000105X 4175 4175 0105 06 0100 TO_ENDING 0.00 (500,000.00) (500,000.00)0105X 4450 4450 0105 ST_ENDING 0.00 0.000105X 4510A1 4510 0105 ST_ENDING 0.00 0.000105X 4610 4610 0105 ST_ENDING 0.00 (19,500,000.00) (19,500,000.00)

----------------------------------Totals: (19,500,000.00) 19,500,000.00

Validation Status: PASS - The Sum of resources EQUAL the total resources.The Sum of the ST account balances EQUALS the Sum of the TO balances.

PeopleSoft GLReport ID: GLS8303 FACTSII ACCOUNTING EDIT VALIDATION REPORT Page No. 1

Run Date 07/01/2002Run Time 07:23:44

User's Report ID: CYCLE_03TSymbol : 02X0105 MAF TSymbol: 02 X0105000000

--- Pre-Edit Validation - This Edit Validates that SGL Accounts are associated with Valid RT7 Values.

Fund Acct SGL Acct Fund Grp TAgcy TAcct TRP CatB Pgm CYR RT7 Attribute PTD Amount Valid RT7 Values

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

0105X 4450 4450 0105 S2 0.00 0.00 0.00-----------------------------------

Totals: 0.00 0.00

Validation Status: PASS - The Sum of resources EQUAL the total resources.The Sum of the S1 account balances EQUALS the Sum of the S2 balances.

--- Accounting Edit 4 - Budgetary accounts related to Anticipated Items are not allowed to have balances at the end of the 4th quarter.

Account SGL Acct Ending Balance

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Validation Status: PASS - Each of anticipated accounts has a zero balance.

--- Accounting Edit 5 - This edit validates that the sum of the Fund Resources (FR) accounts are equal the sum of the Fund Equity (FE) accounts. (SF-2108).

Fund Acct SGL Acct Fund Grp TAgcy TAcct TRP CatB Pgm CYR Attribute Begin Balance PTD Balance FE Amount FR Amount

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------0105X 1010 1010 0105 FR_END 0.00 0.000105X 1010 1010 0105 FR_END 0.00 20,000,000.00 20,000,000.000105X 1010 1010 0105 FR_END 0.00 (500,000.00) (500,000.00)0105X 4450 4450 0105 FE_END 0.00 0.000105X 4450 4450 0105 FE_END 0.00 0.000105X 4510A1 4510 0105 FE_END 0.00 0.000105X 4510A1 4510 0105 FE_END 0.00 (500,000.00) (500,000.00)0105X 4510A1 4510 0105 FE_END 0.00 500,000.00 500,000.000105X 4610 4610 0105 FE_END 0.00 (19,500,000.00) (19,500,000.00)

---------------------------------------------Totals: (19,500,000.00) 19,500,000.00

Validation Status: PASS - The Sum of the Fund Equity account balances equals the Sum of the Fund Resources balances.


Run Date 07/01/2002Run Time 07:23:44


--- Accounting Edit 3 - The Sum of all accounts that are type S1 (Credits) must be equal to the Sum of all accounts) that are type S2 (Debits).

Fund Acct SGL Acct Fund Grp TAgcy TAcct TRP CatB Pgm CYR Attribute Begin Balance S2 Amount S1 Amount

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Validation Status: N/A - There were NO Postings or MAF Records that had a RT7 Value.

--- Accounting Edit 7 - This Edit checks the Fund Balance Supplied by Treasury with the Fund Balance accumulated for the Agency.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Validation Status: PASS - The Fund Balance With Treasury balances equal the Fund Balance with Treasury from the MAF File. (19,500,000.00).

--- Accounting Edit 10 - This edit validates that the balance of the sum of certain accounts has no balance beyond the cancelling year.

Group Balance

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------This Accounting Edit is only relevant For Treasury Symbols in their Cancelling Year. This one is not.

--- Accounting Edit 11 - This edit validates that the balance of the sum of certain accounts has a normal Debit or Credit balance.

Group/Account Balance Condition

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------No footnotes are required.

--- Accounting Edit 12 - This edit will be Valid when the Sum of all Edit12 accounts and the Treasury Net Outlay balance equal zero.

Fund Acct SGL Acct Fund Grp Begin Balance PTD Balance Agency Outlay Calculation Treasury Outlay Amount


Run Date 07/01/2002Run Time 07:23:44


--- Accounting Edit 6 - This edit will compare the RT7 Value from the Treasury Supplied MAF data to the sum of the accounts that have a similar RT7 Value.

RT7 Agency RT7 Bal MAF File RT7 Bal

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Totals: 0.00 0.00

Validation Status: PASS - The FACTS II Net Outlay Balance equals the Treasury Net Outlay Balance for the Current Range of Periods. (0.00).


Run Date 07/01/2002Run Time 07:23:44


--- Accounting Edit 12 - This edit will be Valid when the Sum of all Edit12 accounts and the Treasury Net Outlay balance equal zero.

Fund Acct SGL Acct Fund Grp Begin Balance PTD Balance Agency Outlay Calculation Treasury Outlay Amount

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Edit 01: ATB code does not exist0100010100010101010105031100034050060100064550060101050601010706020100

Edit 08: Invalid SGL Account102010301031404740604070411541174119413141414145414841704175420142104221426142624271442045104590461046204650

PeopleSoft GLReport ID: GLS8310 FACTS I VALIDATION REPORT Page No. 1

Run Date 06/30/2002Run Time 17:06:10Business Unit: FED01

Ledger: LOCAL Fiscal Year: 2002From Period: 3 To Period: 3 Adjustments: None

Fed/ Trading Debit/ BudgetATB Code Account NonFed Partner Credit Amount Delimiter 1 Exch Delimiter 2 SubFunc Delimiter 3 Custodial--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

480149014902

Edit 22: Fed/NonFed attribute not equal to F or N and is required for SGL06010100 2110 C 3,997.00 1 2 3 A06010100 6100 D 3,997.00 1 2 808 3

Edit 56: Budget Subfunction code is invalid for ATB code031100 808

PeopleSoft GLReport ID: GLS8310 FACTS I VALIDATION REPORT Page No. 2



Fed/ Trading Debit/ BudgetATB Code Account NonFed Partner Credit Amount Delimiter 1 Exch Delimiter 2 SubFunc Delimiter 3 Custodial--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

End of Report

Treasury Symbol: 02X0105 Fund: 0105 Bureau: 01 Organization: 200001010 0.00 0.00 0.00 0.00 3101 0.00 0.00 0.00 0.00 4119 0.00 0.00 0.00 0.00 4450 0.00 0.00 0.00 0.00 4510 0.00 0.00 0.00 0.00

-------------------------------------------------------------------------------------------------------------------------------Totals: 0.00 0.00 0.00 0.00

-------------------------------------------------------------------------------------------------------------------------------

Treasury Symbol: 02X0105 Fund: 0105 Bureau: 01 Organization: 210001010 20,000,000.00 0.00 (500,000.00) 19,500,000.00 3101 (20,000,000.00) 0.00 0.00 (20,000,000.00) 3103 0.00 500,000.00 0.00 500,000.00 F 06 4119 20,000,000.00 0.00 0.00 20,000,000.00 4175 0.00 0.00 (500,000.00) (500,000.00) 4450 0.00 0.00 0.00 0.00 4510 0.00 500,000.00 (500,000.00) 0.00 4610 (20,000,000.00) 500,000.00 0.00 (19,500,000.00)

-------------------------------------------------------------------------------------------------------------------------------Totals: 0.00 1,500,000.00 (1,500,000.00) 0.00

-------------------------------------------------------------------------------------------------------------------------------Treasury SymbolTotals: 0.00 1,500,000.00 (1,500,000.00) 0.00

-------------------------------------------------------------------------------------------------------------------------------

Treasury Symbol: 06010100 Fund: 0100 Bureau: 01 Organization: 110001010 9,999,999.00 0.00 0.00 9,999,999.00 3100 (9,999,999.00) 0.00 0.00 (9,999,999.00) 3101 0.00 0.00 0.00 0.00 4119 0.00 0.00 0.00 0.00 4201 9,999,999.00 0.00 0.00 9,999,999.00 4450 0.00 0.00 0.00 0.00 4510 0.00 0.00 0.00 0.00 4610 0.00 0.00 0.00 0.00 4650 (9,999,000.00) 0.00 0.00 (9,999,000.00) 4801 (999.00) 0.00 0.00 (999.00)

-------------------------------------------------------------------------------------------------------------------------------Totals: 0.00 0.00 0.00 0.00

-------------------------------------------------------------------------------------------------------------------------------

PeopleSoft GLReport ID: GLS8311 FACTS I TRIAL BALANCE Page No. 1



FACTS I Attributes:Fed/ Trd Budg

Account Beginning Balance Debit Credit Ending Balance Nfed Prtnr Exch SFunc Cust--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Treasury Symbol: 02X0105 Fund: 0105X Organization: 20000

1010 0.00 20,000,000.00 (20,000,000.00) 0.00

4119 0.00 20,000,000.00 (20,000,000.00) 0.00 P D 107-1 D X

4450 0.00 80,000,000.00 (80,000,000.00) 0.00

4510 0.00 60,000,000.00 (60,000,000.00) 0.00 A

-------------------------------------------------------------------------------------------------------------------------------Totals: 0.00 180,000,000.00 (180,000,000.00) 0.00

-------------------------------------------------------------------------------------------------------------------------------

Treasury Symbol: 02X0105 Fund: 0105X Organization: 21000

1010 0.00 20,000,000.00 0.00 20,000,000.00

1010 0.00 0.00 (500,000.00) (500,000.00)

4119 0.00 20,000,000.00 0.00 20,000,000.00 P D 107-1 D X

4175 0.00 0.00 (500,000.00) (500,000.00) P 107-2 D 06 0100

4450 0.00 40,000,000.00 (40,000,000.00) 0.00

4510 0.00 60,000,000.00 (60,500,000.00) (500,000.00) A

4510 0.00 500,000.00 0.00 500,000.00 A

4610 0.00 20,500,000.00 (40,000,000.00) (19,500,000.00)

PeopleSoft GLReport ID: GLS8312 FACTS II TRIAL BALANCE Page No. 1


Request Report ID: CYCLE_03Fiscal Year: 2002From Period: 1 To Period: 3 Adjustments: 900

FACTS II Attributes:AUT DEF PLaw CAT CBS RIF AVT TRP

Account Beginning Balance Debit Credit Ending Balance BOR BEA YRB TAG TAC ADF FUN CYR--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

AGENCY LOCATION CODE: 11000002

COLLECTIONSTreasury Symbol: 19X0192

Source: Accounts ReceivableBus ItemUnit Customer ID Item Line Seq #FED01 EESC001 EE-MTSC02 0 1 1014 F200

10000 BELGIUM AR_ITEM1 12/31/2001 100.00

FED01 EESC001 EE-MTSC02 0 2 1014 F200 10000 BELGIUM AR_ITEM1 12/31/2001 (100.00)

FED01 EESC001 EM-MTSC01 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 (100.00)

FED01 EESC001 EM-MTSC01B 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 100.00

FED01 EESC001 EM-MTSC02 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 100.00


FED01 EESC001 EM-MTSC04-01 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 (100.00)

FED01 EESC001 EM-MTSC04-02 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 (180.00)

FED01 EESC001 EM-MTSC04-02B 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 100.00

FED01 EESC001 EM-MTSC05-02 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 170.00

FED01 EESC001 EM-MTSC05-02B 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 (100.00)

PeopleSoft GLReport ID: GLS8400 SF224 TRANSACTION DETAIL REPORT Page No. 1

Run Date 02/21/2003Run Time 15:48:21

Business Unit: FED01Agency Location Code: 11000002Fiscal Year: 2001Accounting Period: 12 Account Fund Entry Event Confirm Date AmountBud Ref Class

Dept Oper Unit Product ProgramProject ID

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


FED01 EESC001 EM-MTSC06CR 0 1 1014 F200 10200 ALBERTA AR_ITEM1 12/31/2001 150.00





----------------------------------- (60.00)-----------------------------------

Source: Accounts Receivable Direct JournalsDepositBus Unit Deposit ID Seq #FED01 1 1 1013 F200

10200 ALBERTA AR_DJ 12/31/2001 (200.00)

----------------------------------- (200.00)-----------------------------------

Source: JournalsJournal ID Date Unpost Seq Line

No Journal data found for this Treasury Symbol

Total Collections for Treasury Symbol 19X0192 (260.00)-----------------------------------

Total Collections for Agency Location Code 11000002 (260.00)-----------------------------------


Run Date 02/21/2003Run Time 15:48:21



---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

DISBURSEMENTSTreasury Symbol: 19X0192

Source: Accounts PayableBus Unit Voucher ID Unpost Seq Template Payment Cnt Vchr LineFED01 00000075 0 PAYMENT 1 99999 APVOUCHER 06/14/20011004 F200

10200 ALBERTA (9,782.22)

----------------------------------- (9,782.22)-----------------------------------

Source: JournalsJournal ID Date Unpost Seq LineGL84SF1202 12/03/2001 0 3 1013 F200

10200 ALBERTA SFCASH002 12/03/2001 (7,500,000.00)

GL84SF1202 12/03/2001 0 4 1014 F200 10200 ALBERTA SFCASH003 12/03/2001 (5,500,000.00)

----------------------------------- (13,000,000.00)-----------------------------------

Total Disbursements for Treasury Symbol 19X0192 (13,009,782.22)-----------------------------------

Total Disbursements for Agency Location Code 11000002 (13,009,782.22)-----------------------------------

Net Collection/(Disbursement) Total for Agency Location Code 11000002 (13,010,042.22)===================================


Run Date 02/21/2003Run Time 15:48:22



---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

End of Report

0105X 0105 20000 1010 0.00 0.00 0.00 0.00

0105X 0105 20000 3101 0.00 0.00 0.00 0.00

0105X 0105 20000 4119 0.00 0.00 0.00 0.00

0105X 0105 20000 4450 0.00 0.00 0.00 0.00

0105X 0105 20000 4510 0.00 0.00 0.00 0.00

Total for Organization 20000 : 0.00 0.00 0.00 0.00

_________________________________________________________________________________________________________________________________________________________________________________

0105X 0105 21000 1010 20,000,000.00 0.00 < 500,000.00> 19,500,000.00

0105X 0105 21000 3101 < 20,000,000.00> 0.00 0.00 < 20,000,000.00>

0105X 0105 21000 3103 0.00 500,000.00 0.00 500,000.00

0105X 0105 21000 4119 20,000,000.00 0.00 0.00 20,000,000.00

0105X 0105 21000 4175 0.00 0.00 < 500,000.00> < 500,000.00>

0105X 0105 21000 4450 0.00 0.00 0.00 0.00

0105X 0105 21000 4510 0.00 500,000.00 < 500,000.00> 0.00

0105X 0105 21000 4610 < 20,000,000.00> 500,000.00 0.00 < 19,500,000.00>

Total for Organization 21000 : 0.00 1,500,000.00 < 1,500,000.00> 0.00

_________________________________________________________________________________________________________________________________________________________________________________

Total for Fund Group 0105 : 0.00 1,500,000.00 < 1,500,000.00> 0.00

_________________________________________________________________________________________________________________________________________________________________________________

Total for Appropriation 0105X : 0.00 1,500,000.00 < 1,500,000.00> 0.00

_________________________________________________________________________________________________________________________________________________________________________________

PeopleSoft GL

Report ID: GLS8500 FEDERAL TRIAL BALANCE Page No. 1

Run Date 07/01/2002

Run Time 07:32:33

Bus. Unit: FED01--IT Services Agency



Currency Code: USD

Appropriation Fund Group Organization Alt Acct Beginning Balance Debit Credit Ending Balance

TAS: 060103

AR00000663 02/28/2002 USER1 2002-02-28 09:54:58 -2.92 0.00 808 C 001 NN 001 BAL0103 0103

10000

X

1020

B2002

AR00000663 02/28/2002 USER1 2002-02-28 09:54:58 0.00 -2.92 808 C 001 NN 001S BAL0103 0103

10000

X

1340

B2002

AR00000693 02/28/2002 USER1 2002-04-04 08:54:22 -2.92 0.00 808 C 001 NN 001 BAL0103 0103

10000

X

1020

B2002

AR00000693 02/28/2002 USER1 2002-04-04 08:54:22 0.00 -2.92 808 C 001 NN 001S BAL0103 0103

10000

X

1340

B2002

AR00000650 RD3OV3 02/28/2002 USER1 2002-02-28 22:09:23 25.00 0.00 808 C 001 NN 001S BAL0103 0103

10000

X

1360

B2002

AR00000650 RD3OV3 02/28/2002 USER1 2002-02-28 22:09:23 0.00 25.00 808 C 001 NN 001S X BAL0103 0103

10000

X

5320

B2002

AR00000635 RD4CR7 02/28/2002 USER1 2002-02-28 19:54:00 2.92 0.00 808 C 001 NN 001 BAL0103 0103

10000


Report ID: GLS8501 TRANSACTION REGISTER Page No. 1

Run Date 07/31/2002

Run Time 11:17:25

Bus. Unit: FED01 -- IT Services Agency

Ledger Grp: RECORDING -- Actuals Ledger Group


Fiscal Year 2002

From Period 5 To Period 5

Source: All Journal ID All Journal Status: All

Trans ID Trans Ref Acctg Dt Fund Group Appropriation

Organization Program

Project Object Class

TransactionPart

Trading Partner Account

Bud Ref Debit Credit Date/Time User ID FNF TRP ENE BSF CNC AUT DEF PL CAT CBS RIF AVT TRP BOR BEA YRB TAG TAC ADF FUN CYR

T-SYMBOL 11 F3845

Balance Forward 703,126.42 3,591.32 0.00 0.00

9,253.55 16 Receipts for Budget Susp Accts 11448530 Current Activity

Total Activity 9,253.55

Cumulative Totals 703,126.42 12,844.87 0.00 0.00

Ending Balance 715,971.29

This T-SYMBOL is not an attribute to any FUND_CODE. No GL data provided.

T-SYMBOL 11 F3845044

Balance Forward 836,210.53 90,596.23 295,679.62 0.00

7,696.83 16 Receipts for Budget Susp Accts 11448729 Current Activity

88,742.17 16 Receipts for Budget Susp Accts 11446207

61 Disbursements 2,652.58 11446207

Total Activity 96,439.00 2,652.58

Cumulative Totals 836,210.53 187,035.23 298,332.20 0.00

Ending Balance 724,913.56

GL Balance Forward 0.00

GL Receipts 0.00

GL Disbursements 0.00

GL Ending Balance 0.00

Difference *** 724,913.56


Ending Balance < 748,182.09>


GL Receipts 0.00



Difference *** < 748,182.09>


Ending Balance 0.00


GL Receipts 0.00



Ending Balances match. No difference to report.


Ending Balance < 24,568.59>


GL Receipts 0.00


PeopleSoft GL

Report ID: GLS9500 FUND BALANCE WITH TREASURY RECONCILIATION - EXPENDITURE AND RECEIPT ACCOUNTS Page No. 1

Run Date 01/15/2003

Run Time 17:39:00



Fiscal Year:2002 Undisbursed Appropriations Account Information

Period: 2

Forward Appropriation Curr YR Appropriation Transaction Code/Description Receipts/Disbursements Non-Expense Transfers ALC Reference#

��

SF1219 STATEMENT OF ACCOUNTABILITY AGENCY LOCATION CODE 13010011 ACCOUNTING PERIOD ENDED 2001-12-04 SECTION 1 - GENERAL STATEMENT OF ACCOUNT PART A - TRANSACTIONS DURING PERIOD AFFECTING ACCOUNTABILITY

1.00 ACCOUNTABILITY BEGINNING OF PERIOD $7,500,000.00

2.00 INCREASES IN ACCOUNTABILITY 2.10 CHECKS ISSUED CURRENT PERIOD < $2,000,000.00> 2.11 CHECKS ISSUED/ADJUSTMENTS (TFS FORM 5206) < $933,333.33> 2.12 CHECKS ISSUED/ADJUSTMENTS - OTHER $0.00 2.30 OTHER TRANSACTIONS < $2,000,000.00> 2.34 DISCREPANCIES IN D.O. ACCOUNTS - CREDITS $0.00 2.36 PAYMENTS BY ANOTHER D.O. $0.00 2.37 TRANSFERS FROM OTHER D.O. $0.00 2.80 OPAC PAYMENTS & COLLECTIONS $0.00

2.90 TOTAL INCREASES IN ACCOUNTABILITY < $4,933,333.33>

3.00 SUBTOTAL $2,566,666.67

4.00 DECREASES IN ACCOUNTABILITY 4.10 NET DISBURSEMENTS < $2,000,000.00> 4.20 DEPOSITS PRESENTED/MAILED TO BANK $0.00 4.30 OTHER TRANSACTIONS $0.00 4.34 DISCREPANCIES IN D.O. ACCOUNTS - DEBITS $0.00 4.36 PAYMENTS FOR ANOTHER D.O. $0.00 4.37 TRANSFERS TO OTHER D.O. $0.00

4.90 TOTAL DECREASES IN ACCOUNTABILITY < $2,000,000.00>

5.00 TOTAL ACCOUNTABILITY CLOSE OF PERIOD $4,566,666.67

PART B - ANALYSIS OF OFFICER'S ACCOUNTABILITY 6.10 DEPOSITS IN BANKS $0.00 6.20 CASH ON HAND AND IN TRANSIT TO TREASURY $0.00 6.50 ADVANCES TO AGENTS $0.00 7.00 RECEIVABLES AND DEFERRED VOUCHER CHARGES $0.00 8.00 TOTAL ACCOUNTABILITY $0.00

End of Report

Standard Form 1220 STATEMENT OF TRANSACTIONSAccording to Appropriation, Fund and Receipt Account

Name of Disbursing Officer Department or Agency

IT Services Agency

Location Bureau

IT No Value

No Value

TEST

TEST

TEST

TEST DC TEST

United States

Accounting Period Ended Agency Location Code (ALC)

02/10/2002 19000001

Appropriation, Fund or Receipt Account Receipts and Collections Credited Gross Disbursements

to Appropriation or Fund Accounts

(1) (2) (3)

1920201 $750,000.00 $250,000.00

Column Totals .......................... $750,000.00 $250,000.00

NET TOTAL REPORTED ON LINE 4.10 of SF 1219 (Column 3 minus column 2) ...... < $500,000.00>

Name and Phone of Contact Signature and Title of Certifier DATE

Documents

PeopleSoft General Ledger 8.8 PeopleBook€¦ · Contents General Preface About These PeopleBooks .....xxv PeopleSoft Application Prerequisites.....xxv PeopleSoft Application Fundamentals.....xxv