UT2.WBS Release and Auc Creation
UT2.WBS Release and Auc Creation
UT2.WBS Release and Auc Creation
You cannot change the status from Released to Created, as actual values from, for instance, purchase orders or confirmations may
have been posted
AUC is Asset under construction where some assets are in construction phase and cost needs to capture through internal order for the time being.
Once asset is fully completed then cost would be transferred to another cost object (E.g. Cost center) and settle with final asset.
The released WBS only will accept the FI posting like MIRO. At the time of releasing the WBS it is mandatory to provide the Investment profile to
WBS element, so that system will create the AUC in the background using the investment profile assigned asset class.
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, after creating the WBS it should be released for booking the material or services against to the same WBS. The
released WBS only will accept the FI posting like MIRO. At the time of releasing the WBS it is mandatory to provide the Investment profile to
WBS element, so that system will create the AUC in the background using the investment profile assigned asset class.
Organizational Data:
1.4 Prerequisites
WBS hierarchy should be created under the project.
WBS with CRTD status.
2. STEPS
No. BUSINESS PROCESS STEPS T-CODE/- INPUT DATA / SPECIAL OUTPUT DATA / RESULT TESTER / OK /
PROGRAM INFORMATION TEAM / ROLE ERROR
010 Open Project CJ20N/CJ12 VBCO PS
No. BUSINESS PROCESS STEPS T-CODE/- INPUT DATA / SPECIAL OUTPUT DATA / RESULT TESTER / OK /
PROGRAM INFORMATION TEAM / ROLE ERROR
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