Professional Documents
Culture Documents
Change History:
Date Modified Modified By Brief Description of Change
Cross References
This document can be utilized for unit testing, module testing, and integration testing documentation.
For the testing to be complete all issues occurred should be logged in this document, and solutions should be in place.
SECTION I: OVERVIEW
1.1 Scenario Objective/Description
MSRDC – For VBSL project, Firstly, you create the Project Definition. Then, each WBS is created independently and given a Level Number,
which determines where in the hierarchy it is placed. Each WBS carries lots of information, such as Organization, Dates, Special Settings,
Project Type, who is responsible etc. All of this is discussed in detail later.
VBSL project considering Schedule – H for EPC work. There are other projects to be created for other than EPC work like Authority Engineer
Work, System Integrator Work etc.
Organizational Data:
1.4 Prerequisites
WBS hierarchy should be ready in the form of Schedule H.
2. STEPS
No. BUSINESS PROCESS STEPS T-CODE/- INPUT DATA / SPECIAL OUTPUT DATA / RESULT TESTER / TEAM / OK /
PROGRAM INFORMATION ROLE ERROR
010 Create Project definition CJ20N VBCO PS
No. BUSINESS PROCESS STEPS T-CODE/- INPUT DATA / SPECIAL OUTPUT DATA / RESULT TESTER / TEAM / OK /
PROGRAM INFORMATION ROLE ERROR
Select check box
PE Planning Element
ACC act Account assignment on
requirement
Save.
3. ERROR REPORT
Enter error messages and notes, and/or attach screen dumps at end of document.
Note:
Category: 1 = Master Data Change, 2 = Configuration Correction, 3 = Bug Correction, 4 = Other
Priority: 1 = Serious show stopper, 2 = Need modification but not immediate,
3 = Cosmetic change
4. ERROR RESOLUTION
Step# Action taken Action taken Resolution Status
by date
O = Open
R = Resolved
5. TECHNICAL SIGNOFF
Date Person Module Signature Comments
6. BUSINESS SIGNOFF
Date Person - USER Department Signature Comments