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
/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Document Control
Change Record

1
Date

Author

Versi
on

Change Reference

Reviewers

Name

Position

Distribution

Copy
No.

Name

Location

1
2
3

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: 285220020.doc

(v. DRAFT 1 )

Open And Closed Issues For This Deliverable

10 of 13

TE.040 Test
/var/www/apps/conversion/tmp/scratch_3/285220020.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........................................................................................ 10
Closed Issues......................................................................................10

File Ref: 285220020.doc

(v. DRAFT 1 )

Open And Closed Issues For This Deliverable

10 of 13

/var/www/apps/conversion/tmp/scratch_3/285220020.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: 285220020.doc

(v. )

Open And Closed Issues For This Deliverable

10 of 13

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test Cases
Description

1.
1.

Defining
an
Accounting
Structure

2.

Passing
Journal Entries

3.

Inter-Division
Entries
&
Reconciliation
Import of Data
from
subledgers
&
legacy
systems
FSG Reports

4.

5.

File Ref: 285220020.doc

(v. )

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.
This event will cover a group of
activities, which will be carried under
the GL function at period closing.
This event will cover the procedures
adopted for passing & reconciliation of
Inter-Division entries.
This event lists down how the data will
flow in GL from various sub-ledgers.

The FSG reports will be used for building

reports for FRIDA, Annual Plan etc.

Open And Closed Issues For This Deliverable

10 of 13

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test specifications Defining Accounting Structure

Scenario
Step

Test
Step

1.1

Role

Action
or Path

Define Set
of books &
Account
structure

Set>Key>Segment
Setup>Calendar
Setup>Currency
Setup> Books
The set of books will be
built using a calendar
Nov- to Dec , Curr as INR
& with the 6 segment
structure

Expected Results

Actual Results

Pass

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. Organisation
2. Location
3. Cost center
4. Natural account
5. Products

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.

1.5

File Ref: 285220020.doc

Foreign
Currency
transactions

(v. )

Application should allow transactions in all

above-mentioned foreign currencies.
However, for this foreign currency
transactions should record different
conversion type and rates.
Transactions recorded in foreign currency
are to be converted in Indian Rupee at
appropriate rates, which include even
Open And Closed Issues For This Deliverable

Status

10 of 13

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Scenario
Step

Test
Step

Role

1.6

Accounting
Calendar

1.7

Open/Close
Periods

1.8

Data
Integrity

1.9

Data access

1.10

Coding Logic

File Ref: 285220020.doc

(v. )

Action
or Path

Expected Results

Actual Results

userdefined rates.
The accounting period should be year
ending on 30th November every year.
System should allow for tax purposes to
draw reports from 01-Apr to 31- Mar
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.
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.
Accesss should be allowed to the data
relating to respective business divisions
and cost centers
Coding logic should be such that it will
facilitate groupings for the purpose of
financial statements

Open And Closed Issues For This Deliverable

10 of 13

Status

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test Specifications Passing of Journal Entries

Scenario
Step

Test
Step

2.1

2.3

2.4

2.5

Role
Create
Recurring JV
tempalate

Reversal of
provision
entries of
previous
accounting
period
Approval of
journal
before
posting
Journal entry
in foreign
currency

2.6

Query on
journal

2.7

Creation of
separate
batches
Printing of
journal
register

2.8

File Ref: 285220020.doc

(v. )

Action
or Path

Expected Results

Actual Results

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
Entries for provision of
expesnses are to be to be
reversed in next period

All journal entries passed

should be approved before
posting and after every
modification
Entires should be allowed
to be recorded in Foregin
currency and the same
should be available for
revaluation.
Query should be allowed on
the bassis of any of the
following crieteria:

Categories

Sources

Period

Currency
Journal entries are to be
allowed to be entered
singly or in batches
System should allow
printing of journal register
for a specific period or for
range of numbers
Open And Closed Issues For This Deliverable

10 of 13

Status

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Scenario
Step

Test
Step

2.9

2.11

File Ref: 285220020.doc

Role
Printing of
journal
register for
adjusting
period
Identification
of foreign
currency
expenditure

(v. )

Action
or Path

Expected Results

Actual Results

System should allow

printing of journal register
for entries passed in
adjusting period.
System should provide for
identifying overseas cost

Open And Closed Issues For This Deliverable

10 of 13

Status

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test Test Specifications Import of data

Scenario
Step

Test
Step

8.1

8.4

8.5

8.6

File Ref: 285220020.doc

Role
Avaialability
of audit trail
from import
JV to
transaction.
Import of
data from
modules by
summary
Import of
data from
modules by
details
Import of
data should
be
automatic.

(v. )

Action
or Path

Expected Results

Actual Results

Drilldown upto
transaction level should
be available in GL so that
base entry can be
viewed.
The date transferred from
sub-ledger will be
summary balance
transfer for day/ period
specified.
The data transferred from
sub-ledger will be
individual entry.
The data enterd into subledger should be
transferred to GL
automatically by a predefined schedule say at
non-peak hours.
Optionally users can
import on need basis.

Open And Closed Issues For This Deliverable

10 of 13

Status

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test Specifications Inter division entires and reconciliation

Scenario
Step

Test
Step

9.1

File Ref: 285220020.doc

Role
Accountant

(v. )

Action
or Path
Inter division elimination
entries

Expected Results

Actual Results

Status

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

Open And Closed Issues For This Deliverable

10 of 13

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Test Test Specifications Defect Log

Defect
ID
Number

Test
Step
Referen
ce

File Ref: 285220020.doc

Module Name

(v. )

Defect
Description

Resolution

Re-Test
By

Re-Test
Date

Open And Closed Issues For This Deliverable

10 of 13

Pass/Fai
l

Status
(open,
closed, in
process)

/var/www/apps/conversion/tmp/scratch_3/285220020.doc

Open And Closed Issues For This Deliverable

Open Issues

ID

Issue

Resolution

Responsibility Target
Date

Impact
Date

Resolution

Responsibility Target
Date

Impact
Date

Closed Issues

ID

Issue

File Ref: 285220020.doc

(v. )

Open And Closed Issues For This Deliverable

10 of 13