Cash Management and Cash Position Worksheet Implementation at Boise Inc

Session #3489

Rich HarveyManager, PeopleSoft Business AnalystsBoise Inc.richharvey@boiseinc.com

1

• Two business– Paper and Packaging Division – Public Company– Wood Products Manufacturing and Distribution – Private

Company

• Boise’s upgrade journey– November 1996 - PeopleSoft 5.12

• Accounts Payable• Asset Management• General Ledger• Project Costing

– November 2002 – PeopleSoft 7.5– April 2003

• PeopleSoft 7.5 Billing• PeopleSoft 7.5 Accounts Receivables

– November 2005 – PeopleSoft 8.8– January 2008 - PeopleSoft Cash and Deal Management– October 2008 – PeopleSoft 9.0 2

• Boise’s recent history

– October 2005 – Boise Cascade Corporation was taken private by an equity firm. The businesses taken private; in general terms, consisted of operations for Wood and Paper.

– February 2008 – The Paper side of the business was taken public while the Wood side remained private. The support teams continue to support both the public and the private businesses out of one database.

– Strong relationship between the Technology and Business Analysts teams.

3

Boise’s Implementation Strategy

January 1, 2008 – Implemented the Bank Reconciliation process using electronic BAI files.

August 1, 2009 – Implemented PeopleSoft’s Prior Day and Current Day Cash Position Worksheet functionality.

Currently – Implement the Deal Management functionality to track debt and investment activities.

Partnered with an independent contractor who provided both training and consulting services

4

Boise’s Building Blocks

The following pages will provide a partial glimpse of the steps Boise used during the implementations of the BAI/BSP process and the CWP implementation.

5

Bank Statement (Page 1 of 3) – Began working early with the banks to receive the electronic bank file into PeopleSoft

6

Statement Codes define on Page 10

Bank Statement (Page 2 of 3) – Note the Statement Code (195) and the Activity Type (MISC)

7Statement Codes define on Page 10

Bank Statement (Page 3 of 3) – Note the Addenda description of TEST

8

Building Block 1 – Layout Catalog (PeopleSoft Delivered)

9

Building Block 2 – BAI2 Code Mappings (Page 1 of 2)4 Mappings required – BANK_ID, BANK_STMNT_CODE, RECON_TRANS_CODE and STMT_ACTIVITY_TYPE

10

Building Block 2 – BAI2 Code Mappings (Page 2 of 2)

11

Building Block 3 – Bank Statement Balance Codes (Page 1 of 2)

12

Building Block 3 – Bank Statement Transaction Codes (Page 2 of 2)

• Building Block 3 – Bank Statement Balance Codes (Page 1 of 2)

13

Building Block 4 – Accounting Template

14

Building Block 5 – Statement Activity Type

15

Building Block 6 – Bank Statement Accounting

16

Building Block 7 – Bank (Page 1 of 2)

17

Building Block 7 – Bank (Page 2 of 2)

18

The prior page prints has allowed Boise to process the daily BAI files which has automatically recorded better than 96% of the daily transaction over the last year.

The prior processes are also the building blocks for the Cash Position Worksheet implementation outlined in the following presentation.

19

Building Block 1 - Views used in CPW tree development found at Setup Financials/Supply Chain > Product Related > Treasury > Position Source. Some views were altered to include additional fields while several were copied/renamed to use in our process.

20

Define the Tree at the root level.

21

Pages 21-24 all define the BCLLC CASH POSITION Tree Node

Define the positions at the Root Node. (Positions defined on Page 20)

22

Define Tree Wide Options at the root node.

23

Define Node Properties at the root node.

Note – This page shows the Position Sources that Boise added that provides greater detail during the CPW processes.

24

Cash Position Tree – Previous page prints defined the structure for the top node of BCLLC CASH POSITION.

25

Next series of Page Prints will show a node that defines a value that will produce a line in the CPW report. Next several page prints defines the node of JPMC 5391 BEG BAL

26

Selecting the edit icon to the right of the JPMC05391 BEG BAL node produces this page print. This is a detail (defined as non-recursive) node and its total definition appear in page prints following this page print.

27

The Positions for this detail node are inherited from the root node (Page 23) and require no further alteration. (See Page 22)

28

The ‘Tree Wide Options’ for this is inherited from the root node (presented earlier) and does not need any alteration.

29

Select the Position where the value on the Bank Statement is stored. This instructs the process where to find the value for this node.

30

This tab for the detail node (accessed by pressing ‘Selection Criteria’ on Page 30) instructs the system where to go to get the value for the CPW report.

31

Statement Codes defined in Pages 6 and 7

Quick review as to where the values are stored that will be used in the CPW tree.

32

This is a partial repeat of Page 6

Now that all of the preliminaries have been completed the CPW process can begin

33

Populate the ‘Position Manager Options’ page as desired

34

Closing the ‘Position Manager Options Page’ and selecting one of your positions will produce the following series of page prints

35

Pressing on the feet for ‘JPMC 5391 Cash’ on Page 35 produces;

36

Pressing on the feet for ‘JPMC 5391 Wire In’ on Page 36 produces

37

Pressing on the feet for ‘OTHER 5391 Wire In’ on Page 37 produces

38

Pressing on the feet for ‘JPMC 5391 Wire Out’ on Page 38 produces

39

Pressing on the feet for ‘OTHER 5391 Wires’ on Page 39 produces

40

Q&A

Security using PeopleSoft Trees, Query and SQL+

Session #3489

Rich HarveyManager, PeopleSoft Business AnalystsBoise Inc.richharvey@boiseinc.com

41