TE40 General Ledger Version 1.0

AIM

TE.040 TEST CASES

ITW SIGNODE INDIA LTD.

Implementation of Oracle - General Ledger

Author: Sunil/AVSR

Creation Date: February 4, 2003

Last Updated: February 4, 2002

Document Ref: ITW-GL-001

Version: DRAFT 1

Approvals:

TE.040 Test /tt/file_convert/563dba4c550346aa9aa46547/document.doc

Document Control

Change Record

1

Date Author Version

Change Reference

Reviewers

Name Position

Distribution

Copy No.

Name Location

123

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

File Ref: document.doc (v. DRAFT 1 )

Open And Closed Issues For This Deliverable 10 of 13

TE.040 Test /tt/file_convert/563dba4c550346aa9aa46547/document.doc

Contents

Document Control...................................................................................ii

Overview.....................................................................................................1

Test Cases..................................................................................................2

Test specifications – Defining Accounting Structure....................3

Test Specifications – Passing of Journal Entries.............................5

Test Test Specifications – Import of data.........................................7

Test Specifications – Inter division entires and reconciliation. .8

Test Test Specifications –Defect Log.................................................9

Open And Closed Issues For This Deliverable..............................10

Open Issues............................................................................................10Closed Issues.........................................................................................10

File Ref: document.doc (v. DRAFT 1 )


/tt/file_convert/563dba4c550346aa9aa46547/document.doc

Overview

This Test Cases documents the steps needed to test the application function with respect to the General Ledger.

Test Cases will be built to measure the quality of the entire application system, using acceptance and system test sequences and scripts. The scripts for all business processes are based on the Mapped Business Requirements (BR.030).

ThisTest Cases will include the following types of testing:

A. Acceptance test cases

Processes and process steps

Data capturing for reports

Integration across modules

Integration/interfaces with legacy system

Customization

System requirement

Workflow and Alerts

Security matrix

Document sequencing

Accouting treatment

File Ref: document.doc (v. )



Test Cases

Seq Date Time Test Name Description Teste Test Status Pass/Fail Notes

1.1. Defining an Accounting Structure

This event defines the common structure or framework which will be used for financial & MIS reporting & which will be used by all function like Receivables, Payables, Fixed Assets etc.

2. Passing Journal Entries

This event will cover a group of activities, which will be carried under the GL function at period closing.

3. Inter-Division Entries & Reconciliation

This event will cover the procedures adopted for passing & reconciliation of Inter-Division entries.

4. Import of Data from sub-ledgers & legacy systems

This event lists down how the data will flow in GL from various sub-ledgers.

5. FSG Reports The FSG reports will be used for building reports for FRIDA, Annual Plan etc.




Test specifications – Defining Accounting Structure

ScenarioStep

TestStep Role

Actionor Path Expected Results Actual Results Status

1.1 Define Set of books & Account structure

Set>Key>SegmentSetup>CalendarSetup>CurrencySetup> Books

The set of books will be built using a calendar – Nov- to Dec , Curr as INR & with the 6 segment structure

The entries passed in various sub-ledger should get posted to this Set-of Books using the accounting structure.

The period end balances will get automatically carried forward & at year end the revenue items will be transferred to retained earnings account defined at the Set of Books level.

Set of books must provide for capturing data based on following:

1. Organisation2. Location3. Cost center4. Natural account5. Products

Pass

1.4 Enabling currencies in which transactions may be recorded

Defining currencies System should allow transactions in following currencies:

Indian Rupee US Dollar Singapore Dollar Ausrallian Dollar

All transactions in Set of books are to be converted and recorded in Indian Rupee as functional currency.

Application should allow transactions in all above-mentioned foreign currencies. However, for this foreign currency transactions should record different conversion type and rates.

1.5 Foreign Currency transactions

Transactions recorded in foreign currency are to be converted in Indian Rupee at appropriate rates, which include even userdefined rates.

1.6 Accounting The accounting period should be year




ScenarioStep

TestStep Role


Calendar ending on 30th November every year. System should allow for tax purposes to draw reports from 01-Apr to 31- Mar

1.7 Open/Close Periods

Entries should be allowed only in open periods and for the purpose of monthly ending it should partly close the period as regards regular entries and finally close after pasing of all year end finalization entries.

1.8 Data Integrity

The data should be secured across organisation, location and profit centers. Secondly, within company, location, division and profit center the access should be restricted to certain account values or range of values for different users. Further, certain combination of segments may also be not allowed.

1.9 Data access Accesss should be allowed to the data relating to respective business divisions and cost centers

1.10 Coding Logic Coding logic should be such that it will facilitate groupings for the purpose of financial statements




Test Specifications – Passing of Journal Entries

ScenarioStep

TestStep Role


2.1 Create Recurring JV tempalate

System should allow definfing templates for journal entries, which will be used frequently to pass journal entires.

Recurring entries templates will be defined for monthly depreciation entries provision entries

2.3 Reversal of provision entries of previous accounting period

Entries for provision of expesnses are to be to be reversed in next period

2.4 Approval of journal before posting

All journal entries passed should be approved before posting and after every modification

2.5 Journal entry in foreign currency

Entires should be allowed to be recorded in Foregin currency and the same should be available for revaluation.

2.6 Query on journal

Query should be allowed on the bassis of any of the following crieteria:

Categories Sources Period Currency

2.7 Creation of separate batches

Journal entries are to be allowed to be entered singly or in batches

2.8 Printing of journal register

System should allow printing of journal register for a specific period or for range of numbers

2.9 Printing of journal

System should allow printing of journal register




ScenarioStep

TestStep Role


register for adjusting period

for entries passed in adjusting period.

2.11 Identification of foreign currency expenditure

System should provide for identifying overseas cost




Test Test Specifications – Import of data ScenarioStep

TestStep Role


8.1 Avaialability of audit trail from import JV to transaction.

Drilldown upto transaction level should be available in GL so that base entry can be viewed.

8.4 Import of data from modules by summary

The date transferred from sub-ledger will be summary balance transfer for day/ period specified.

8.5 Import of data from modules by details

The data transferred from sub-ledger will be individual entry.

8.6 Import of data should be automatic.

The data enterd into sub-ledger should be transferred to GL automatically by a pre-defined schedule say at non-peak hours. Optionally users can import on need basis.




Test Specifications – Inter division entires and reconciliation

ScenarioStep

TestStep Role


9.1 Accountant Inter division elimination entries

Identification of entires for elimination at the time of consolidation so that elimination can be easily done.

The actual Inter-division entries will be passed separately from the normal entries using the Inter-Division accounts. This account will be mapped in the FSG for divisional MIS but at the time of Financial reporting this will be mapped to one cell so that their ultimate effect will be zero.

PASS




Test Test Specifications –Defect Log

Defect ID Number

Test Step Reference

Module Name Defect Description

Resolution Re-Test By Re-Test Date

Pass/Fail Status (open,

closed, in process)




Open And Closed Issues For This Deliverable

Open Issues

ID Issue Resolution Responsibility

Target Date

Impact Date

Closed Issues

ID Issue Resolution Responsibility

Target Date

Impact Date



TE40 General Ledger Version 1.0

Documents

Transcript of TE40 General Ledger Version 1.0