te.040_gl

28
AIM TE.040 SYSTEM TEST SCRIPT General Ledger Implementation Author: Creation Date: March 4, 2015 Last Updated: March 4, 2015 Document Ref: Version: Approvals:

Upload: surya-maddiboina

Post on 09-Sep-2015

13 views

Category:

Documents


1 download

TRANSCRIPT

TE.040 System Test Script

Doc Ref: TE.040 System Test ScriptDecember 29, 2003

AIM

TE.040 System Test Script

General Ledger Implementation Author:

Creation Date:December 21, 2003Last Updated:February 10, 2006Document Ref:

Version:

Note: Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->OptionsView and checking the Bookmarks option in the Show region.Approvals:

Note: To add additional approval lines, press [Tab] from the last cell in the table above.

Copy Number_____

Note: You can delete any elements of this cover page that you do not need for your document. For example, Copy Number is only required if this is a controlled document and you need to track each copy that you distribute.

Document Control

Change Record

1DateAuthorVersionChange Reference

Reviewers

NamePosition

Distribution

Copy No.NameLocation

1

2

3

4

5

Note: The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

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.

Contents

iiDocument Control

Overview1Century Date Compliance1System Test Sequences2System Test Specifications < Maintaining Cross Validation rules >3System Test Specifications < Define New Account COA Values >4System Test Specifications < Define New Accounting Periods >5System Test Specifications < Define Conversion Rates >6System Test Specifications < Open / Close GL Accounting Periods >7System Test Specifications < Enter Functional Currency Journals >8System Test Specifications < Enter Foreign Currency Journals >9System Test Specifications < Journal Revision And Posting >10System Test Specifications < Define / Generate Recurring Journals >11System Test Specifications < Reverse Journal Entries >12System Test Specifications < General Ledger Interface >13System Test Specifications < Consolidation Run >14System Test Specifications < Period End Revaluation >15System Test Specifications < Reporting >16Defect Log17Open And Closed Issues For This Deliverable18Open Issues18Closed Issues18

Note: To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Overview

This System Test Script documents the steps needed to test the integration of application extensions with the target application system with respect to the General Ledger process.

System testing measures the quality of the entire application system, using system test sequences and scripts. You must create scripts for all business processes based on the Mapped Business Requirements (BR.030); however, the focus of business solution testing is confirming individual business processes, while business system testing focuses on confirming the collective application system. This system test will include the following types of testing:

Integrated Business Processes

Security Testing

Century Date Compliance

In the past, two character date coding was an acceptable convention due to perceived costs associated with the additional disk and memory storage requirements of full four character date encoding. As the year 2000 approached, it became evident that a full four character coding scheme was more appropriate.

In the context of the Application Implementation Method (AIM), the convention Century Date or C/Date support rather than Year2000 or Y2K support is used. It is felt that coding for any future Century Date is now the modern business and technical convention.

Every applications implementation team needs to consider the impact of the Century Date on their implementation project. As part of the implementation effort, all customizations, legacy data conversions, and custom interfaces need to be reviewed for Century Date compliance.

Testing activities need to make sure that all interfaces and application extensions are coded for Century Date compliance. System test scripts should include steps for testing Century Date compliance.

System Test Sequences

Note: The tables in this deliverable contain sample data that should be used as an example only. Remove all sample data before completing your final deliverable.

Sequence #General Ledger Test NameDescriptionTesterTest StatusPass/FailNotes

1. Maintaining Cross Validation rulesMaintaining Cross Validation rulesActive

2. Define New Account Flexfield ValuesDefine New Account Flexfield ValuesActive

3. Define New Accounting PeriodsDefine New Accounting PeriodsActive

4. Define Conversion RatesDefine Conversion RatesActive

5. Open / Close GL Accounting PeriodsOpen / Close GL Accounting PeriodsActive

6. Enter Functional Currency JournalsEnter Functional Currency JournalsActive

7. Enter Foreign Currency JournalsEnter Foreign Currency JournalsActive

8. Journal Revision And PostingJournal Revision And PostingActive

9. Reverse Journal EntriesReverse Journal EntriesActive

10. Enter Budget JournalsEnter Budget JournalsActive

11. General Ledger InterfaceGeneral Ledger InterfaceActive

12. Consolidation RunConsolidation RunActive

13. Period End RevaluationPeriod End RevaluationActive

14. ReportingReportingActive

System Test Specifications < Maintaining Cross Validation rules >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

1.1Maintaining Cross Validation RulesGL Supervisor(N) Setup > Financials > Flexfields > Key > Rules (M) View > Find

Search for your accounting flexfield structure

Enter the validation Rule Name and Description.

Enter the Error Message that to be used to guide the user on his journal entry accounting Flexfield to correct and validate combination.

Enter the Error segment that shows the user what segment to update. It leaves the cursor in this segment whenever a segment combination violates this cross-validation rule.

Enter the Cross Validation Rule Elements:

First Select Include for all the accounting range:

From: 00-0000-000000-0000-0000-0000To: 99-9999-999999-9999-9999-9999

Second Select Exclude for the invalid combinations that Violates this Cross Validation rule.

Save your Work.- During the Journal entry only accounting Valid combinations is accepted by the system, and any accounting combinations that violates any of the Cross validation rules, the rule error message appears to the user.

System Test Specifications < Define New Account COA Values >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

2.1Defining New Chart of Accounts segment Values

GL Supervisor

(N) Setup > Financials > Flexfields > Key > Values

Select Application: (Oracle General Ledger)

Select Title: (Accounting Flexfield)

Select Structure

Select the segment that you want to add to it a new value

(B) Find

Move to Values section

(M) File > New

Enter the new value

Enter the new value description

Only if entering a value for the Natural account Segment, you must specify the qualifier Account type (Asset, Liability, Expense, Revenue, Ownership/Stockholder's Equity)

Save your Work- New value is added to the Chart of Accounts and appears in the list of values showing the accounting values During the Journal Entry.

2.2Deactivate Chart of Accounts segment valueGL Supervisor(N) Setup > Financials > Flexfields > Key > Values

Select Application: (Oracle General Ledger)

Select Title: (Accounting Flexfield)

Select Structure

Select the segment that you want to add to it a new value

(B) Find

Move to Values section

(M) View > Find, to search for the value you want to deactivate

Uncheck the Enabled check box, in order to deactivate the COA vaule

Save your Work The COA value is deactivated. The list of values is not showing the deactivated value during the Journal Entry.

System Test Specifications < Define New Accounting Periods >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

3.1Defining New Accounting PeriodsGL Supervisor(N) Setup> Financials > Calendar > Accounting (M) View > Find

(Select appropriate calendar)

Enter the New Period Prefix

Select the Period Type

Enter the Year this Period Related to

Enter the Sequence of this Period in its Year

Enter the Quarter Number where this Period Belongs to

Enter the Starting Calendar day where this Period Starts

Enter the Ending Calendar day where this Period Ends

Mark for the Adjusting period Check Box, Only if this period is an adjusting period

Save your Work A new period is added to the company accounting periods

The new defined periods its status is closed and can be opened later on.

System Test Specifications < Define Conversion Rates >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

4.1Defining Daily Conversion RatesGL Supervisor

(N) Setup> Currencies > Rates > Daily (B) Press Enter by date range

Select the Currency you want to enter its conversion rate

Enter the Date Range From Date and To Date for this conversion rate

Select the Type as Corporate

Enter the Conversion Rate

(B) Apply (to apply this rates to the date range specified)

Save your work Foreign currency journals can be entered and uses the specified corporate conversion rates

4.2Defining Period Conversion RatesGL Supervisor

(N) Setup> Currencies > Rates > PeriodUse the revaluation rate to revalue account balances that are denominated in a foreign currency at the end of period

Select the Currency you want to enter its conversion rate

Select the Balance Type you want to revaluate with this period conversion rate (Actual / Budget)

Select the accounting Period to which the rates apply. For actual balances, you can select any open, future-enterable, or closed accounting period. For budget balances, you can select any period up to the last period of the latest open budget year

Enter the revaluation rate. Enter the rate that you multiply your foreign currency amount by to determine the functional currency equivalent

Save your work You can run revaluation using this period conversion rates

System Test Specifications < Open / Close GL Accounting Periods >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

5.1PR_GL_01

EV_GL_02 Close / Open PeriodOpen First Accounting Period

GL Manager

(N) Setup> Open/Close Choose the first period to open from List of Values

(B) Press Open Period First Accounting period is Opened

The Request Completed Normal

5.2Closing Accounting PeriodGL Manager

(N) Setup> Open/Close Choose the Period you want to close

Select from list of values to change its Status to Closed The Period is Closed and no one can enter, post or update Journals in to this Period

5.3Opening Next Accounting PeriodGL Manager

(N) Setup> Open/Close (B) Open Next Period in order to open the next period

You can select Open from the list of values to open any closed period After the request completed, the Period is opened for Entry and Posting

The following 1 period is opened as Future Entry Period

System Test Specifications < Enter Functional Currency Journals >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

6.1PR_GL_02

EV_GL_03

Source document arrivalEntering Functional Currency Journals GL Accountant(N) Journal > Enter

(B) New Journal

Enter Journal Header Information:

Enter Journal Name: (Can be Characters, Numbers or Both, or you can leave it empty)

Journal Period: (The Default period is Last Open Period / Batch period)

Journal Date: (The effective date for the Journal)

Journal Category:

Journal Description: (This description will default to all journal lines)

Control Amount: (Optional, used to control the total of your journal lines)Note: If Journal Name is not Specified the System Automatically gives the Journal a name Enter Lines Information:

Line Number:

Line Account:

Line Amount: (Debit)

Line Description: (Defaulted from the Journal Description)

Line Amount: (Credit)

Line Description: (Defaulted from the Journal Description)

Enter all required journal lines:

Save your Journal The Journal Saved

The Document Number Created

6.2Journal InquiryGL

Accountant

(N) Inquiry > Journal

You Can Query on Entered Journals by the Following Attributes:

Journal Name & Batch Name

Period

Category

Currency

Journal Source (Manual / Other Modules)

Posting Status (Posted, Unposted, or Error)

Document Numbers (From / To)

Creation Dates (From / To) Journal Entries that was recorded in step 6.1 could be retrieved for revision or correction

6.3Printing the Journal VoucherGL

Accountant

(N) Other > Report > Run

(B) Single Request Chose the report name as (Journal General (132 Char) Report, for unposted journals)

Enter parameters for the journal entry recorded in step 6.1: (Journal Name, Currency, Period) Submit the Request with no of Copies equal 1 Request Completed Normal and the Report Printed

Data output is accurate and reflects actual data entered

System Test Specifications < Enter Foreign Currency Journals >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

7.1PR_GL_02

EV_GL_03

Source document arrivalEntering Foreign Currency JournalsGL Accountant(N) Journal > Enter

(B) New Journal

Perform the same steps of Entering Functional Journals as mentioned in senario step 6.1

Select the Foreign Currency

Select the Date for conversion rate

Select the conversion Type and Rate.

Example:

Save your Journal The Foreign amount Converted to the Functional Amount Based on the Rate The Journal Saved

The Document Number Created

7.2Journal InquiryGL

Accountant

(N) Inquiry > Journal

Query on the entered Journals from the Journals window itself, using the same search components as in scenario step 6.2

Suggestion: Query on the Foreign Currency Journals by selecting the required currency Foreign Currency Journal Entries that was recorded in step 7.1 could be retrieved for revision or correction

7.3Printing the Journal VoucherGL

Accountant

(N) Other > Report > Run

(B) Single Request Select the report from the list of values

Select Journals Foreign Currency (132 Char) to review Foreign Currency Journals

According to the report parameters you can print the following data:

All Journals and Batches

Single Batch

Single Journal

Submit the Request with no of Copies equal 1

Request Completed Normal and the Report Printed

Data output is accurate and reflects actual data entered

System Test Specifications < Journal Revision And Posting >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

8.1PR_GL_03

EV_GL_02Printing the unposted Journal VoucherGL Supervisor(N) Other > Report > Run

(B) Single Request Chose the report name as (Journal General (132 Char) Report, for unposted journals)

Enter parameters for the journal entry recorded in step 6.1: (Journal Name, Currency, Period)

Submit the Request with no of Copies equal 1 Request Completed Normal and the Report Printed

8.2Posting the JournalsGL Manager(N) Journals > Post

Select the required period, balance type (Actual), required batch name or leave blank to retrieve all unposted batches

(B) Find to retrieve required unposted batches

Mark the Check Box for the batches you want to post

You can review any batch before posting

(B) Post

Batch status is Posting The request completes with no errors (the batch posted)

The Accounts balances reflected in the Trial Balance Standard Report

8.3Account Inquiry GL Supervisor(N) Inquiry > Account Select the Accounting Periods you want to inquire the Account in it

Choose if you want to inquire for the Account balance on a Single Currency (Select the Currency) or All Currencies

Choose the Primary Account Balance Type you want to inquire (Actual / Budget / Encumbrance)

Press Tabs till you reach to the Find Accounts Popup window

Enter from: Accounts To: Accounts you want to inquire about

(B) Show Balances

(B) Journal Details if you want more details

You can query the original journal entry by pressing (B) show full journal

In case of this Account Journals entered in AP or AR or Assets, you can press (B) Drilldown to review the Sub ledger Details

In case there is a budget amount on this Account Choose the Secondary Account Balance Type as Budget and enter the Budget Name then Press (B) Show Variance

Account Balance information appears The Account Balance is correct

The Variance is Calculated correct

8.4Account Balances ReportsGL

Supervisor(N) Other > Report > Run

(B) Single Request Select your reports from the List of Values, to view the Accounts Movements and Balances run the following reports:

- Account Analysis (132 / 180 Char)

- General Ledger (132 /180 Char)

- Trail Balance Report Report output is consistent with actual data

System Test Specifications < Define / Generate Recurring Journals >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

9.1PR_GL_07

EV_GL_07Define Recurring JournalsGL Supervisor(N) Journals > Define > Recurring Enter a unique Name and optional Description for the batch

(B) AutoCopy (If you want to copy entries from an existing recurring journal batch

Note: You should group your recurring entries into one batch to speed processing.

Enter the recurring journal entry Name:

Select the recurring journal entry Category:

Select the recurring journal entry Currency:

Optionally enter a range of Active Dates to limit the use of the recurring entry to a specific time

(B) Press Lines (to enter the recurring journal lines information)

Enter a Line number:

Select the recurring journal line GL Account:

Enter an optional Line Description:

Enter a Formula for the line if this is a formula recurring entry. Otherwise, enter an amount for standard entries

Note: you can leave the Formulas blank to create skeleton journal entries

Note: If the formula amount is positive, your account will be debited. If the formula amount is negative, your account will be credited

Formula Operators:

Associate an operator with each step of the formula (Use Enter to store the associated number or Use (+) to add, (-) to subtract, (*) to multiply, (/) to divide the associated number into the most recently stored number)

Enter all remaining lines for the recurring journal entry

Save your work Recurring Journal Entry is ready to be generated

9.2Generate Recurring JournalsGL Supervisor(N) Journals > Generate > Recurring Select the Recurring Batch you want to generate

Select the Accounting Period to create an unposted journal batch

(B) Press Generate

A concurrent request submitted to create the unposted journal batches (The resulting journal batch is named :

If you generated skeleton journal entries, use the Enter Journals window to complete the journal information

Post the recurring journal batches to update account balances Recurring Journals created and posted

The Accounts balances updated

System Test Specifications < Reverse Journal Entries >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

10.1Reversing Incorrect JournalsGL Supervisor(N) Journal > Enter

(B) Find

(B) Review Journal

(B) More Details Find the Journal you want to reverse

(B) Review Journal

(B) More Details

Select the Period you want to reverse journal in it

Select the Reverse Method you want to Reverse with (Switch Dr/Cr or Change Signs)

(B) Press the Reverse Journal Reversal Request completes normal An unposted Reversal Journal is created

10.2Post the Reversed JournalsGL Supervisor(N) Journals > Post Find the Reversal Journals created By: (Period, Journal Name, Batch Name)

Select the journals you want to post

Post the Journals Reversed Journals posted

The Account Balance for these transactions net to Zero balance again

System Test Specifications < General Ledger Interface >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

11.1Transfer from Sub Ledgers to General LedgerImporting Journals

GL Supervisor(N) Journals > Import> Run Select the Source you need to import from List of Values.

(B) Press Import The request completes with no errors

11.2Review Import Request StatusGL Supervisor

(N) Other > Requests (B) Press Find to view all your requests

Find your Import request by request number

If the request Completed Normal press view output Button

The output file is an execution report showing if there is any error in the journals you are importing, error lines and the error code for each line (like EF04). At the end of this report there is an Error Key to find out the error code meaning (Like EF04: These segment values are not a valid account. Check your cross validation rules)

If the request Completed with error press Log File Button, In this case you should inform your System Administrator The request exist

The Output File Viewed

The Log File Viewed

Note: the request may complete with status Normal but when you view the output file the journals may have errors. This different than the request Completed with Error

11.3Correcting Imported Journals GL Supervisor

(N) Journals > Import > Correct Find the required journal from the Journal Source

Correct the journal lines

Save your work

(B) Press Import (repeat step 12.1) When you save the correction the line status will change to Corrected

The required journal imported & can be posted

11.4Viewing Imported JournalsGL Supervisor(N) Journals > Enter Query the Imported Journal Batch

Review the Journal Header Information

Review the Journal Lines Information The Document Number Created

All Imported Journals Information exists and correct

11.5Posting Imported JournalsGL Supervisor(N) Journals > Post Query the required batch

Mark the Check Box

(B) Press Post The Batch Posted

The Account balances updated

11.6Account InquiryGL Supervisor

(N) Inquiry > Accounts Select the Period range you want to inquire for it

Select the Currency

Press Tabs till you reach the Find Accounts Popup window

Enter From: Accounts To: Accounts you need to inquire

(B) Press Show Balance

(B) Press Journal Details if you want more details

(B) Press Show full Journal to view the original journal entry The Account Balance is Correct

11.7Account ReportsGL Supervisor(N) Other > Report > Run Print Account Balance Reports (General Ledger) to review the account balance The report completed Normally

The Account Balance is Correct

System Test Specifications < Consolidation Run >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

12.1PR_GL_08

EV_GL_02

Period EndRun Consolidation TransferGL Supervisor

(N) Consolidation > Transfer > Data

Select the consolidation mapping you want to transfer

Select Actual for the Balance Type

Select the Amount Type (YTD, PTD)

Select the subsidiary's accounting Period that you want to consolidate

Enter the Standard Period to which you want to consolidate in your parent set of books

(B) Press Select Accounts to specify the account ranges you want to consolidate

Uncheck Include All Accounts

Enter the Account Low and High for each range you want to consolidate

(B) Press Run Options

Select Run Journal Import option and Audit Mode check boxes

(B) Choose Transfer to launch a concurrent process to transfer your subsidiary data to your parent The transfer process completed normal

The balances transferred from the subsidiary set of books to the parent

12.2Reviewing & Posting the created JournalsGL Supervisor(N) Journals > Enter

(N) Journals > Post Query the created Journal Batch

Review the Journal Header Information

Review the Journal Lines Information

(B) More Actions

(B) Post The Doc. # Created

All created Journals Information correct

The Batch Posted

The Account balances updated

12.3Print Triabl Balance ReportGL Supervisor(N) Other > Report > Run Print Triabl Balance Report to review the accounts balances The report completed Normally

The Account Balance is Correct

12.4Run FA What if AnalysisFA SupervisorFixed Assets This Process will be maintained in the Fixed Assets Test Script

System Test Specifications < Period End Revaluation >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

13.1PR_GL_01

EV_GL_02

Period EndRun RevaluationGL Supervisor

(N) Currency > Revaluation

Revaluation adjusts liability or asset accounts that may be materially understated or overstated at the end of a period due to a significant fluctuation in the exchange rate between the time the transaction was entered and the end of the period

Open the Revalue Balances window

Enter the accounting Period for the balances you want to revalue

Enter the Unrealized Gain/Loss Account

Select one of the following Currency Options:

Single Currency: Select Currency & enter Rate to use (if you didnt define Period rate for this period and currency)

All Currencies: To revalue all foreign currencies (GL revalues each foreign currency balance only if a period-end rate exists for that currency and period)

Enter an Account Low and High to revalue accounts that fall within that range

Repeat this step to enter multiple ranges (You can reuse account ranges from your last revaluation)

(B) Press Revalue The Revaluation Execution Report is automatically generated, there is no errors

Unposted revaluation journals batch created and ready for revision and Post

13.2Posting Revaluation Journals batch

GL Supervisor (N) Journals > Post After reviewing your revaluation batch you should run post to effect your accounts balance

You post the revaluation batch for period end financial reporting

If revalued amount becomes higher than the original amount, the difference recorded as an unrealized gain & if the revalued amount is lower than the original, the difference recorded as an unrealized loss

Query the required batch, select it and Press (B) Post The period end financial reporting correct and reflects the fluctuation in the exchange rate

13.3Reversing Revaluation Journals

GL Supervisor(N) Journal > Enter

(B) Find

(B) Review Journal

(B) More Details

(N) Journals > Post After reporting on revalued balances, reverse the revaluation journals in the following month to restore the account balances to the original amounts, so that the balance can be revalued in the coming periods till the balance become zero

Find the Revaluation Journal, (B) Review Journal, (B) More Details

Select the Period: (Reverse revaluation journal in the next period)

Select the Reverse Method you want to Reverse with (Switch Dr/Cr or Change Signs)

(B) Press Reverse Journal

(B) More Actions, Post Revaluation Journal In the following period, Find the Reversed Revaluation Journals created

Select the batch you want to post, (B) Press Post Reversal Request completes normal The Revaluation Journals batch reversed and posted in the next period The Account Balance for these transactions net to Zero balance again

System Test Specifications < Reporting >

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepEventTestStepRoleActionor PathTest Step DetailsExpected ResultsActual ResultsStatus

14.1PR_GL_07

EV_GL_09Print Standard Reports

GL Supervisor

(N) Other > Report > Run

(B) Single Request Select from LOV the following reports:

Trail Balance Detail

Trail Balance Expanded

Trial Balance Summary 1

General Ledger 132 Char

General Ledger Foreign Currency (132 Char)

Note: You have to enter the required parameters for each report Trial Balance data is correct and consistent with the actual data

14.2Generate The FSG ReportsGL Supervisor(N) Reports > Request > Financial Select the report Name

Select the accounting period

Select the Currency

(B) Press Submit to Run the report The request completes with no errors

The FSG Reports generated consistent with the data

Defect Log

Defect ID NumberTest Step ReferenceModule NameDefect DescriptionResolutionRe-Test ByRe-Test DatePass/FailStatus (open, closed, in process)

Open And Closed Issues For This Deliverable

Note: Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution.

When this deliverable is complete, any open issues should be transferred to the project- or process-level Risk and Issue Log (PJM.CR.050) and managed using a project level Risk and Issue Form (PJM.CR.050). In addition, the open items should remain in the open issues section of this deliverable, but flagged in the resolution column as being transferred.

Open Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

Closed Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

System Test Specifications < Reporting > 3 If > 1 18 of 23 = - Sec1 22 iii 18 of 22

General Ledger Implementation File Ref: TE040-Test-Script-GL

_1133599557.xlsSheet1

CurrencyUSD

Rate TypeUser

Rate1.229