Anda di halaman 1dari 9

AIM

TE.050 SYSTEMS INTEGRATION TEST


SCRIPT
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: May 24, 1999
Last Updated: May 28, 1999
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
TE.050 Systems Integration Test Script Doc Ref: <Document Reference Number>
May 28, 1999

Document Control

Change Record
3

Date Author Versio Change Reference


n

24-May- <Author> Draft No Previous Document


99 1a

Reviewers

Name Position

Distribution

Copy Name Location


No.

1 Library Master Project Library


2 Project Manager
3
4

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.

<Subject> Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TE.050 Systems Integration Test Script Doc Ref: <Document Reference Number>
May 28, 1999

Contents

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

Overview.....................................................................................................1
Century Date Compliance.....................................................................1
Systems Integration Test Sequences..........................................................2

Systems Integration Test Specifications.....................................................3

Data Profile.................................................................................................4

Defect Log...................................................................................................5

Open and Closed Issues For This Deliverable.............................................6


Open Issues...........................................................................................6
Closed Issues.........................................................................................6

<Subject> Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. DRAFT 1A )
Company Confidential - For internal use only
Doc Ref:

Overview
The Systems Integration Test Script tests the integration between the
target application system and legacy and third-party applications with
respect to a specific systems integration. A separate test script will be
established for each integration between Oracle Applications and third-
party or legacy systems.

The systems integration test measures the coexistence of your


application system with the neighboring application systems in the
enterprise with which it must interface. The systems integration test uses
test scripts comprised of system test sequences from two or more
systems that interface. The systems integration test checks the
integration points between separate systems to confirm that they are
able to work together from a process flow perspective and from a data
integration perspective.

Systems Integration Test Scripts address the following:

• systems integration sequences using converted data


• lock testing simulating user load, executing identical scenarios
• batch window test on full converted data volumes (for example,
financial close period, MRP run, and Payroll run)

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. Systems integration
test scripts should include steps for testing century date compliance.

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only
Doc Ref:

Systems Integration Test Sequences

Sequenc Date Time Test Name Description Tester Test Status Pass/Fail Notes
e#

APTI10 TBD TBD Invoice Import Imports invoices from J.S. Elcaro Active Pass
external system

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only
Doc Ref:

Systems Integration Test Specifications

Scenari Test Action Expected Actual


o Step Role or Path Expected Results Actual Results Cycle Time Cycle Time Status
Step

APTI10 Run Superuser NORR Production job will Normal end-of job > 2 min 1.5 Min. Active
Payables complete normally with no
Invoice exceptions
Import

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only
Doc Ref:

Data Profile

Scenari Business Data Business


o Object Condition Rule Type Status
Step

APTI10 External Invoices Entered Invoices Pay vendor invoices Open Active
Invoices

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only
Doc Ref:

Defect Log

Defect ID Test Step Module Name Defect Resolution Re-Test By Re-Test Date Pass/Fa Status
Number Referenc Description il (open,
e closed, in
process)

1 APTI10 AP Invoice Import Developer B. Dinger 01/01/00 Pass Closed


failed reloaded
invoice import
file

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only
Doc Ref:

Open and Closed Issues For This Deliverable

Open Issues

ID Issue Resolution Responsibility Target Impact


Date Date

Closed Issues

ID Issue Resolution Responsibility Target Impact


Date Date

Open and Closed Issues For This Deliverable


File Ref: 39155691.doc (v. )
Company Confidential - For internal use only