Asset Acceptance Order

8/6/2019 Asset Acceptance Order

http://slidepdf.com/reader/full/asset-acceptance-order 1/43

FUNCTIONAL DESIGN

Russian Localization

FDD_CLEF095_Asset Acceptance Order

Applications Release: 12.0

Author: Baburao Marla

Creation Date: 5-Mar-2007

Last Updated: 26-Mar-2007

File URL: https://iprojects-files.oracle.com/files/app/FileBrowsePage$PP=$|files$|page$|FileBrowse$CS=7?event=ChangeDir&AFBP=24930427&FBP=MyWorkspaces/Russian%20Localization/RUSSIAN%20LOCALIZATION%20R12/FROM%20ORACLE%20SSI/Documents/Asset_Acceptance_Order_version_1.0.doc

Draft / Version: Version 1.0

Status: IN PROCESS

Template Version: 1.1

Disclaimer: The following is intended to outline our general product direction and is intended for information purposes. Thedevelopment, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.

Copyright©2011 Oracle CorporationAll Rights Reserved

http://opt/scribd/conversion/tmp/scratch25190/%20https://iprojects-files.oracle.com/files/app/FileBrowsePage$PP=$%7Cfiles$%7Cpage$%7CFileBrowse$CS=7?event=ChangeDir&AFBP=24930427&FBP=MyWorkspaces/Russian%20Localization/RUSSIAN%20LOCALIZATION%20R12/FROM%20ORACLE%20SSI/Documents











Document Control

Change Record

Date Author Version Change Reference

5-Mar-2007 Baburao Marla Draft 1A First draft

26-Mar-07 Baburao Marla Draft 1B Changes made as per peer review comments

26-Mar-07 Baburao Marla 1.0 Changes made as per QC Comments Ref:24411

Contributors

Name Organization Title

Akbar Pasha Mohammed Technical Consultant

Reviewers

Name Role Title Date Reviewed

Sampath Srinivasan Functional Consultant Staff Consultant 26-Mar-07

Chandu Rao Functional Consultant Principal Consultant 26-Mar-07

Approvers

Name Role Title Date Approved

High-level design components (milestone 1)

Core design components (milestone 2)

Final Functional Design (milestone 3)

Document References

Document Title Type of Reference Document Location

Item_10_06_MD050 OC-1_ASSETACCEPTANCEORDER_1_5.doc MD.050 https://iprojects-files.oracle.com/files/app/FileBrowsePage$PP=$|files$|page$|FileBrowse$CS=17?event=ChangeDir&AFBP=3824321&FBP=MyWorkspaces/Russian%20Localization/RUSSIAN%20LOCALIZATION%2001/From%20Oracle%20SSI/Release

Demo RecommendationsBusiness Requirements Overview Oracle Corporation Confidential - For Oracle internal use only Page 3 of 43



Table of Contents

1. Introduction .................................................................................................................................................. 8

1.1 Scope of this document ....................................................................................................................8

1.2 Purpose of this Document ................................................................................................................8

1.3 Intended Audience .......................................................................................................................... 8

2. Definitions .....................................................................................................................................................9

3. Business Requirements Overview ............................................................................................................ 10

3.1 Requirements Addressed ............................................................................................................... 10

3.1.1 Business Requirements ............................................................................................................................. ....103.1.2 Security Requirements .............................................................................................................................. ...103.1.3 Data Privacy Requirements ...........................................................................................................................103.1.4 Performance Requirements .................................................................................................................. ...... ...10

3.2 Requirements Not Addressed ........................................................................................................ 11

4. Solution Analysis ........................................................................................................................................12

4.1 Solution Overview ......................................................................................................................... 12

4.1.1 Asset Acceptance Order ...............................................................................................................................12

4.2 Business Model: Objects ................................................................................................................12

4.3 Business Model: Functions ............................................................................................................12

4.4 Business Model: Process ...............................................................................................................12

4.5 User Interactions ............................................................................................................................ 12

4.6 Assumptions ..................................................................................................................................12

4.7 Constraints .....................................................................................................................................12

4.8 Technology Considerations ........................................................................................................... 12

5. The localization DFF’s use OA Framework.Impacts, Dependencies & Uptake ..................................13

5.1 Impacts ........................................................................................................................................... 13

5.1.1 Impact on Assets ...........................................................................................................................................135.1.2 Impact on Other Products and Initiatives ......................................................................................................135.1.3 Impact on Existing Users ..............................................................................................................................13

5.2 Dependencies ................................................................................................................................. 13

5.3 Uptake ............................................................................................................................................13




5.3.1 Product Team Instructions ............................................................................................................................135.3.2 Uptake Considerations ..................................................................................................................................135.3.3 Uptake Tools .................................................................................................................................................13

5.4 Documentation ............................................................................................................................... 13

6. Solution Components ................................................................................................................................ 14

6.1 Solution Component List ...............................................................................................................14

6.1.1 Solution to Requirement Mapping ................................................................................................................14

6.2 Solution Flows ............................................................................................................................... 14

7. Solution Component: <Page Name> Page (BLAF UI) ...........................................................................15

8. Solution Component: <Form Name> Form (Professional UI) .............................................................. 16

9. Solution Component: “CLE Asset Acceptance Order” Report ........................................................... 17

9.1 Objective ........................................................................................................................................17

9.2 Rules and Examples .......................................................................................................................17

9.3 Parameters ...................................................................................................................................... 17

9.4 9.4 Layout ..................................................................................................................................... 18

9.4.1 Report Heading – First Page ............................................................................................................... ...... ....249.4.2 Column Headings – Second Page .................................................................................................................269.4.3 Column Headings – Section 3. Short Individual Characteristics of the Asset.............................................. 289.4.4 Totals .............................................................................................................................................................299.4.5 Summary Section ..........................................................................................................................................29

9.5 Exception Handling ....................................................................................................................... 29

9.6 Log File .......................................................................................................................................... 29

10. Solution Component: <Template Name> XML Publisher Template .................................................30

30

11. Solution Component: <Program Name> Concurrent Program ..........................................................31

12. Solution Component: <API Name> Public API .................................................................................... 32

13. Solution Component: <Workflow Name> Workflow .......................................................................... 33

14. Seed Data .................................................................................................................................................34

14.1 Menus ...........................................................................................................................................34

14.2 Function Security Options ...........................................................................................................34




14.3 Profile Options ............................................................................................................................34

14.4 Messages .....................................................................................................................................34

14.5 Other Seed Data ........................................................................................................................... 34

15. User Procedures .......................................................................................................................................36

16. Upgrade and Migration ........................................................................................................................... 37

17. Demo Recommendations .........................................................................................................................38

18. Test Scenario Recommendations ............................................................................................................ 39

19. Patent Submission Considerations ......................................................................................................... 40

20. Open and Closed Issues ........................................................................................................................... 41

20.1 Open Issues .................................................................................................................................. 41

20.2 Closed Issues ................................................................................................................................41

21. Appendix: Recommended Next Phase .................................................................................................. 42

22. Appendix: Discarded Solutions ............................................................................................................. 43




Table of Figures




1. Introduction

This document is delivered as part of Russian Localization Project for Release 12 of OracleApplications and includes set of reporting form required for Russian Legislature.

This document defines detailed requirements for the Asset Acceptance Order. The document

specifies the report layout, source data for the report fields, formatting, requirements for log fileand data security. This document should be used by development to create technical design of thereport.

1.1 Scope of this document

This document is a functional design for the reporting form “Asset Acceptance Order”

Current document relates to the functionality of the following module of Oracle E-Business Suite(OEBS):

• Assets

1.2 Purpose of this Document

The purpose of this document is to present an overview of the requirements on Asset AcceptanceOrder, functional design, solutions, limitations and their impact on the other components. It isintended to be the single source of information for the technical design, developer’s guide, user and the implementation guides.

1.3 Intended Audience

• Russian Localization team members

• Functional Experts

• SSI Team developers up taking Russian Localization Project.

• QC Team

• RLP Customers




2. Definitions

This solution does not use any new terms.




3. Business Requirements Overview

3.1 Requirements Addressed

3.1.1 Business Requirements

In accordance with the Russian Legislation, the Asset Acceptance Order should be printed onreceipt or issue of the assets (except Building). This report should include the following details:

• Description of the Asset, Location Details, Date of receipt, Date of Issue(retirement),Manufacturer of the Asset and Shareholders

• Asset Information on date of receiving.

• Asset information on the accounting date.

• Short Individual characteristics of the asset.

• Other details of the asset.

• Details containing the person/position Delivering & Receiving and the physical details ofthe asset.

3.1.2 Security Requirements

Not Relevant

3.1.3 Data Privacy Requirements

Standard restrictions for access to information about the assets as implemented in OEBS.

3.1.4 Performance Requirements

No special requirements are required.




3.2 Requirements Not Addressed

There are no excluded requirements.




4. Solution Analysis

4.1 Solution Overview

4.1.1 Asset Acceptance Order

Solution allows user to print report “ Asset Acceptance Order” from Oracle Applications. Thisreport should be issued with Assets Responsibility from the Standard Report Submission(SRS)form.

4.2 Business Model: Objects

The base transactions for this document is Asset created through Mass Additions, Quick Additions, Additions. and Retirements.

4.3 Business Model: Functions

Users issue “CLE Asset Acceptance Order” through SRS form. The report output file can be sentto printer to get hard copy of the document.

4.4 Business Model: Process

In order to issue CLE Asset Acceptance Order, users should perform the following tasks:

• Log into the Oracle Applications with Assets responsibility

• Create a new asset or query an asset created through Mass Additions process.

• Enter information required in DFF Asset Category

• Run CLE Asset Acceptance Order through SRS form either on creation of new asset or retirement or partial retirement of existing asset. Note the Concurrent request number.View the output of completed request.

4.5 User Interactions

Refer point 4.4

4.6 Assumptions

For the successful execution of the Asset Acceptance Order, it is required that:

• Users run Oracle Applications 12.0

• The segments should be defined for Asset Category DFF.

4.7 Constraints

No Constraints

4.8 Technology Considerations




5. The localization DFF’s use OA Framework.Impacts, Dependencies & Uptake

5.1 Impacts

The solution is part of Russian Localization package for Oracle Assets.

5.1.1 Impact on Assets

No Special impact

5.1.2 Impact on Other Products and Initiatives

5.1.3 Impact on Existing Users

No impact

5.2 Dependencies

The solution has dependency on the form RU-63 Specific Asset Information precious metalsform.

5.3 Uptake

5.3.1 Product Team Instructions

Not Applicable

5.3.2 Uptake Considerations

Not Applicable

5.3.3 Uptake Tools

Not Applicable

5.4 Documentation

• RLP User Guide document

• WPTG for Translation




6. Solution Components

6.1 Solution Component List

CLE Asset Acceptance Order is composed of the following components:

• “CLE Asset Acceptance Order” Report

6.1.1 Solution to Requirement Mapping

Solution allows user to print report “ Asset Acceptance Order” from Oracle Applications. Thisreport should be issued with Assets Responsibility from the Standard Report Submission(SRS)form.

6.2 Solution Flows




7. Solution Component: <Page Name> Page (BLAF UI)

Not Applicable.

Not Applicable




8. Solution Component: <Form Name> Form (Professional UI)

Not Applicable.




9. Solution Component: “CLE Asset Acceptance Order” Report

The solution component contains the new report “CLE Asset Acceptance Order” Report. Therewill be neither changes to any existing report nor any reports would become obsolete due to thissolution.

9.1 Objective

• “CLE Asset Acceptance Order” report is required by and complies with the requirementsof Russian Legislation.

• Accountants who are responsible for additions & retirements of the assets.

• The report would be a part of Standard Request Submission (SRS).

• The report would be a single request.

9.2 Rules and Examples

In order to issue the CLE Asset Acceptance Order , users should perform the following tasks:• Log into the Oracle Applications with Assets responsibility

• Create a new asset or query an asset created through Mass Additions process.

• Enter information required in the DFF Asset Category

• Run the CLE Asset Acceptance Order through SRS form either on creation of new assetor retirement or partial retirement of existing asset. Note the Concurrent request number View the output of the completed request.

9.3 Parameters

Parameter Required Default Value LOV

Asset Number Yes No Asset Name together with the Asset Numbers.The user can also enter the asset number manually.

Asset Book Yes No List of Books, the asset is assigned to

Supplier Invoice Number Optional No List to select Invoice ID to be put into thereport parameter. It should also containadditional columns such as Invoice Number,Date, Supplier Name and Amount to helpusers make choice.

Internal Bank Account Optional No List of Bank Accounts of the Operating Unitof the given Invoice.




9.4 9.4 Layout

Solution Component: “CLE Asset Acceptance Order” ReportSolution Component: “<CLE Asset Acceptance Order”Report Name> Report Oracle Corporation Confidential -For Oracle internal use only Page 18 of 43

APPROVED BY APPROVED BY

Manager Of the Supplier Organization Manager Of the Receiver Organization

" " 200 y. " " 200 y.

SEAL SEAL

Form by OKUD

by OKPO

by OKPO

(full name) (position) (signature) (full name)(signature)(position)

<1> Vision Operations

<8>

(subdivision description)

(description)

<6> Moscow, Lenin Prospekt, 33, (095) NNN-NN-NN, (nnn) NNN-NN-NN

(address, phone, fax)

<7> Bank Of Moscow, Current Operations, 012345678910123456789

Unified Form #OC-1

Approved by Goskomstatat of

of 21.01.2003 #7

(bank account)

<5> Santinel Manufacturer Supplier Organization

Code

0306001

<4> Moscow Department, St.Petersburg department, Balance Sheet

(subdivision description)

Receiver Organization

<2> New York, xxxxxyyyyyzzzz, xxxxxxxyyyyyyyyzzz, NNN-NN-NN, (NNN NNN-NN-NN xxxxxxxx xxxxxxxxxxxxxxxxxxxx)

(address, phone, fax)

(description)

<3> Citibank Cash Acct, 00012345410032421

(bank account)




Date

by OKOF

Number

Asset Description

Location at the filling date <20>

(description)

Of the Receiving/Delivering

Of the Asset Object (Except Buildings)

ACTFilling Date

<14>

Documner Number

(rate) (amount)(date)

<21> XXXXXXXXXXXXXXXYYYYYYYYYYYYYZZZZZZZZZZ

(Description)

<23> XXXXXXXXXXXX YYYYYYYYYYYY ZZZZZZZZZZ

State

Registration <18><19> XXXXXXYYYYYYYYYYYYYYYYZZZZZZZZZZZZ

(name, purpose, model)

Employee

NNN

<15>

<16>

<17>

<13>

Number

Depreciation group

Asset

by Manufacturer

Account, Subaccounts

Issued from the Accounting

<12>

Reason of the filling of the act

<10>Date

<11>

CITY.STREET.BUIDING.XXXXXXXXXXX

2. In Foreign Currency*

(order, direction, agreement (with type, charges and other mutters))

<9>Put into Accounting date

Number

* This f ield should be filled in case the purchasing of the asset was in foreign currency

Date

Manufacturer Organization

For Information:

1. Shareholders

QTY Expense Account Address

XXXXXXXXX YYYYYYYYYY ZZZZZZZZZ NN.NNN.NNNN.NNN.NNN




1. Asset Information On the Date Of the Receiving

4b 5b

Months Months

MM MM

2. Asset Information On the Accounting Date

3.Short Individual Characteristics Of the Asset

4. Other Characteristics

Useful Lifetime

xxxxxxxxxxxxxx xxxxxxxx xxxxxxxxxxxx

NN

Cost

Of

Purchasing

Net

Book

Cost

Useful

3 6 7 85a

Years

4a

Years

xxxxxxxxxxxxxxxxxx NNN.0 xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxx

7

Accumulated

Depreciation

Amount

NN NNN NNN.00

5 6

4

xxxxxxxxxxxxyyyyyyyyyyzzzzzzz

1 2 3 4

Weight Nomenclature Number

NN

Precious Materials Content (Metals, Stones, etc.)

Name Of Precious Materials UOM QTY

NN.NNNNNNN

NN NNN NNN.00 NN NNN NNN.00

NN NNN NNN.00

Asset Object, Accessories and Tools

Name Of Detail QTY

NNN years, MM months

DD-MON-YYYY

Manufactured

(year)

Last

Capital

Repair

1 2

Depreciation Method

Description Rate

2 3

At the Moment of Accounting

1

DD-MON-YYYY DD-MON-YYYY

Recoverable Сost

(Years,Months)

2nd page of №ОС-1 form

Lifetime

Date

Place in Service

(initial)

Actual

Time

In Use




The Trial Board

" " 200 y.

position

full namesignature

position

position signature full name

position

not required

Note what is required Note what is not appropriate

Conclusion by the trial board:

he asset object with the current technical conditions

Test Results on

accepted

not accepted backfitting is

required

ddendum. Technical documentation

Chief of board:

Board members:

signature full name

3rd page of form

full namesignature




The Asset Object

Delivered by Received by

" " 200 y. Tab Number " " 200 y .

" " 200 y №

The asset received by person in charge

" " 200 y. Tab number

Accounting department note: Note about the filling of the

The retirement is posted to the book asset accounting card

and the record of the asset book

signature full name signature full name

Document

number

Filling

date

full namesignature

to whom (full name)

position signature

Chief Accountant

given

Chief Accountant

position full name

position

signature

By the letter of

full name






9.4.1 Report Heading – First Page

9.4.1.1 Receiver organization <1>

<1>

If the Invoice Number parameter is set the report prints Operating Unit Description. In the other case the report left the field blank.

9.4.1.2 Address, phone, fax <2>

The report prints the concatenated value of the Location Address(for given Operating Unit) , phone and fax fields. If the Invoice Number is not set the report left this field blank.

9.4.1.3 Bank Account Name & Number<3>

<3>

Bank Account Name & Number of the bank which is used to make the payment for the abovementioned invoice.

9.4.1.4 Subdivision Description<4>

<4>

The report shows all distinct values of the cost center segment descriptions of the expenseaccounts defined in asset assignments. All descriptions should be separated from each other bycomma.

9.4.1.5 Supplier Organization <5>

The report shows Supplier Name derived by the given Invoice.

9.4.1.6 Address, phone, fax <6>

<6>

The report shows concatenated values of the address lines, phone and fax from the supplier sitedefined for the entered Invoice Number.

9.4.1.7 Bank account <7>

<7>

The report shows Bank Name, Bank Account Name and Number of the primary bank account of the supplier

9.4.1.8 Subdivision Description <8>

<8>

Left Blank




9.4.1.9 Put into accounting date <9>

<9>

The report shows Date In Service. The field format is DD-MON-YYYY

9.4.1.10 Issued from accounting <10>

<10>

The report shows Retirement Date if the asset has being retired, or left the field blank. The fieldformat is DD-MON-YYYY

9.4.1.11 Account, sub accounts <11>

<11>

The report shows concatenated values of the COST ACCOUNT associated with the asset.

9.4.1.12 Depreciation group, by OKOF <12>

<12>

The report shows concatenated KFF segments of the asset category.

9.4.1.13 Document Number <13>

<13>

The report shows the Document Number segment of the Asset Category DFF.

9.4.1.14 Filling Date <14>

<14>

The report shows the Filling Date segment of the Asset Category DFF.

9.4.1.15 Number/Asset <15>

<15>

The report shows Asset Number

9.4.1.16 Number/by manufacturer <16>

<16>

The report shows Warranty Number




9.4.1.17 State Registration /Number <17>

<17>

The report shows the State Registration Number of the DFF Asset Category

9.4.1.18 State Registration/Date <18>

<18>

The report shows the State Registration Date of the DFF Asset Category.

9.4.1.19 Asset Description <19>

<19>

The report shows Asset Description

9.4.1.20 Location at the filling date <20>

<20>

The report prints the table with the assignments information: QTY, Employee, Expense Account,Address. The Address should show descriptions of values of asset location. Please use verticalelasticity to show all data.

9.4.1.21 Manufacturer organization <21>

<21>

The report prints Manufacturer

9.4.1.22 Shareholders <23>

<23>

The report shows the Shareholders segment of the Asset Category DFF

9.4.2 Column Headings – Second Page




9.4.2.1 Date/Manufactured - 1

The report prints the Manufactured Date segment from the Asset Category DFF

9.4.2.2 Date/Put in use for the first time - 2

2

The report prints the ’First Put in Use’ segment of the Asset Category DFF

9.4.2.3 Date/Last Capital Repair - 3

3

The report prints the Capital Repair Date segment of the Asset Category DFF

9.4.2.4 Actual Time of Usage – 4a, 4b

4

The report prints the Actual Usage Years segment of the Asset Category DFF into the field # 4aand Actual Usage Months into the field # 4b

9.4.2.5 Useful Lifetime - 5a, 5b

The report prints ‘Years’ and ‘Months’ segments of the Asset Category DFF into fields # 5a and5b.

9.4.2.6 Accumulated depreciation amount - 6

6

The report prints the ‘Accumulated Depreciation’ segment of the Asset Category DFF

9.4.2.7 Net Book Cost - 7

7

The report prints the ‘Net Book Cost’ segment of the Asset Category DFF

9.4.2.8 Cost of purchasing - 8

8

The report prints the ‘Cost of Purchasing” segment of the Asset Category DFF.

9.4.2.9 Recoverable cost at the moment of accounting -1

1

The report prints the Recoverable cost from the corporate book




9.4.2.10 Useful lifetime - 2

2

The report prints value from “Original asset life in months” segment in DFF Asset Category (seeAssumptions).

9.4.2.11 Depreciation method/Description -3

3

The report prints the description of the depreciation method defined in the corporate book

4

9.4.2.12 Depreciation method/Rate - 4

The report prints the rate or lifetime in according to the depreciation method defined in the

corporate book.

9.4.3 Column Headings – Section 3. Short Individual Characteristics of the Asset.

This section sources are described in Item CLE_FD_RU_63_Specific_asset_information. Allfields are shown as it appears in the Navigate->Assets->Asset Workbench->M:Tools->B:CLE FAContent of precious material in Assets

9.4.3.1 Column Name of detail Text field (60 characters) <1>

Name of the asset part, which contained precious or semiprecious materials.

9.4.3.2 Part quantity Number (positive, 6 digits) <2>

Quantity of the part that name was entered in Name of detail field.

9.4.3.3 Name of precious material (LOV) <3>

The name of precious or semiprecious material.

9.4.3.4 Nomenclature number Text field (40 characters) <4>

Nomenclature number of precious or semiprecious material.

9.4.3.5 Units of measure (LOV) <5>

Unit of measure for quantity of precious material.

9.4.3.6 Quantity Number (positive, 6 digits) <6>

Quantity of precious or semiprecious material.

9.4.3.7 Weight Number (positive, 10digits + 2 decimal digits) <7>

Weight of precious or semiprecious material.




9.4.4 Totals

No totals

9.4.5 Summary Section

No totals

9.5 Exception Handling

If the report stops due to any setup issues, detailed explanation should be printed in the log file

9.6 Log File

The report log file should include the following information:

• Report version

• Parameters received

The list of all DFF segments required by the report. If any DFF segments are not set up the reportshould print the unset segment name in the log file and continue execution.




10. Solution Component: <Template Name> XML Publisher Template

Not Applicable






12. Solution Component: <API Name> Public API

Not Applicable.




13. Solution Component: <Workflow Name> Workflow

Not Applicable.




14. Seed Data

• The new DFF’s are required to implement the feature

• There are no changed or entirely new seed data

• There is no obsolete seed data?

14.1 Menus

Not Applicable

14.2 Function Security Options

Not Applicable

14.3 Profile Options

Not Applicable.

14.4 Messages

Not Applicable.

14.5 Other Seed Data

The following Descriptive Flexfields are used for the report CLE: Asset Acceptance Order.

Application

Short Name

Descriptive Flexfield Form/OA

Page

Segment Attribute

FA Asset Category OA Page State Registration Date

FA Asset Category OA Page State registration Number

FA Asset Category OA Page Document Number

FA Asset Category OA Page Document Filling Date

FA Asset Category OA Page Shareholders

FA Asset Category OA Page Manufactured Date

FA Asset Category OA Page First Put in Use

FA Asset Category OA Page Capital Repair Date

FA Asset Category OA Page Actual Usage Years

FA Asset Category OA Page Actual Usage Months

FA Asset Category OA Page Years




Application

Short Name

Descriptive Flexfield Form/OA

Page

Segment Attribute

FA Asset Category OA Page Months

FA Asset Category OA Page Accumulated Depreciation

FA Asset Category OA Page Actual Usage

FA Asset Category OA Page Cost of Purchasing

Not




15. User Procedures

Not Applicable




16. Upgrade and Migration

Not Applicable.




17. Demo Recommendations

Not Applicable.




18. Test Scenario Recommendations

• The feature will be tested covering scenarios for creation of assets, Creation of assets for more than one invoices, Creation of assets for invoices created in different operatingunits, Revaluing the asset, Revalue the asset partially, changing the depreciationmethod/rate

• The report layout and the values passed into the report are the key areas to be tested.




19. Patent Submission Considerations

Not Applicable.




20. Open and Closed Issues

20.1 Open Issues

No. Description Date

Raised

Priority Owner Action Target

Date

1. In the first page of the layout the year is mentioned as200_ . This affectsthe report if it hasto be used beyond2009. So, please

confirm, if we canreplace the above as20__.

26-Mar-07

M Oracle Russia.

2.

3.

Priority: H= High; M=Medium, L=Low

20.2 Closed Issues

No. Description Date

Raised

Priority Owner Resolution Date

Closed

Priority: H= High; M=Medium, L=Low




21. Appendix: Recommended Next Phase

Not Applicable.


