AIM for Business Flows

MD.050 APPLICATION
EXTENSIONS
FUNCTIONAL DESIGN

VITARICH CORPORATION
ASSETS ACCOUNTABILITY
REPORT

Author: FIT Financials Team

Creation Date: 8 November 2017
Last Updated: 11 March 2024
Control Version: <Draft>
Version Number: 1.0

Approvals:
Marian A. Dionisio Date:
VC Representative

Date:
Ananias E. Diokno III
VC Project Manager
Date:
Grace Ogena
FITC Project Manager
Document Control

Change Record

Date Author Version Change Reference

8-Nov-2017 Clarissa Baja Draft 1.0 No previous document

Reviewers

Name Position

Ananias E. Diokno III VC Project Manager

Rowena M. Hocson VC Financials Champion
Marian A. Dionisio VC FA Team Lead
Faith Marie A. Donadillo VC Fixed Assets Champion
Grace Ogena FITC Project Manager

Distribution

Copy No. Name Location

Library Master Project Library

Project Manager

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control ii

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
 Contents

Document Control...................................................................................................................
Topical Essay.............................................................................................................................
Basic Business Needs........................................................................................................
Major Features...................................................................................................................
Definitions..........................................................................................................................
User Procedures................................................................................................................
Business Rules...................................................................................................................
Assumptions......................................................................................................................
Report Descriptions.................................................................................................................
Approach............................................................................................................................
Report Mapping Details and Validation.......................................................................
Report Layout....................................................................................................................
Report Parameters.............................................................................................................
Concurrent Program Description..........................................................................................
When to Run the Program...............................................................................................
Error handling and Reporting.........................................................................................
Launch Parameters...........................................................................................................
Technical Overview.................................................................................................................
Century Date Compliance...............................................................................................
Open and Closed Issues for this Deliverable.......................................................................
Open Issues........................................................................................................................
Closed Issues......................................................................................................................

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control iii

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Topical Essay
This document focuses on functional design and specifies the requirements for processing of
VITARICH Assets Accountability Report program for assets monitoring. It includes the business
requirements, assumptions and pre-requisites as per business needs of VITARICH. This
functional design provides adequate guidance for a technical resource to create technical
specification document.

Basic Business Needs

The VC Assets Accountability Report provides you with the features you need to satisfy the
following basic business needs. You will be able to address the following:
 Properly monitor assets assigned and transferred to each employee per book
 View asset details and details of assignment and transfer

Major Features

VC Assets Accountability Report

Vitarich currently monitors their assets manually. VC Assets Accountability Report will be
provided to be able to address the users’ need. Through this report, they will be able to see all the
assets assigned to employee as of date. This report will also allow them to see the asset details
and details of asset assignment and transfer.

Definitions
List of definitions, acronyms and abbreviations used in this document:

Term Definition
VC Vitarich Corporation
Oracle EBS Oracle E-Business Suite
FA Fixed Assets
LOV List of Values
NA Not Applicable

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 1

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
User Procedures

VC Assets Accountability Report

Step1: Login to Fixed Assets Responsibility
Step2: Submit New Request
Navigate: Reports > Others>Request > Run
Or on the Menu click View > Request
Step3: Select VC Assets Accountability Report
Step4: Enter Parameters

 Asset Book: LOV <List Asset Books>

 Employee: LOV <List of Employee Names>

Step5: Submit Request

Business Rules
The business rules of the reports are the following:
 If asset has no previous owner, previous assignee and previous assignee’s head columns
will be empty.
 Assets that will appear in the report are assets assigned to and transferred to employee
per asset book.
 The report will show all the assets assigned to and transferred to employee at the time
when the concurrent program is run.

Assumptions
This design assumes that the following statements are true:
 Upon successful completion of the report program, the report in the form of PDF
file will be manually retrieved from view output in EBS system.
 In case of transfer, assets with COMPLETED/POSTED status only will appear in
the report.

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 2

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Report Descriptions

Approach
 The Business user runs the custom report when it is needed (on demand) with the set of
input parameters
 The input parameters for the invoice related receipts monitoring report will be by:
o Asset Book
o Employee
 The report will be sorted by Date of Issuance and in descending order (from latest date).
 The reports will be executed by giving inputs to Asset Book and Employee.
 Asset Book parameter default value will be set to VC ASSET BOOK.
 Upon successful completion of the custom report the user will retrieve the PDF output of the
report manually from view output in EBS.

Report Mapping Details and Validation

 Below are the detailed data mapping from the source file to Oracle Target Tables (Double
click the excel icon to view the file)

Report Layout
 Report output to be in PDF format.
 Report output file will be retrieved manually by the user manually from view
output in EBS
 Sample VC Assets Accountability Report:

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 3

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Report Parameters
You run the VC Assets Accountability Report from the Standard Report Submission form. Enter
the following parameters specify the desired reporting options.
 This program will have the following input parameters

SI Parameter Description Displayed Required/ Default Value

No Name (Y/N) Optional Value Set

1 Asset Book Asset Book Yes Required VC ASSET NA

Name BOOK
2 Employee Employee Name Yes Required NULL NA

 Upon successful completion of the custom report the user will retrieve the PDF output of
the report manually from view output in EBS.
 The report can be re-run as required by the Business User.

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 4

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Concurrent Program Description

When to Run the Program

VC Asset Accountability Report concurrent program will be run manually in Oracle EBS as
required by the Business user.

Error handling and Reporting

 User will verify the errors in Oracle EBS log files and take the corrective actions
o User will verify the nature of error(s) whether it is transactional, procedural or
technical error.
o Error(s) must be investigated and corrected before rerunning the report.
o For errors that are technical in nature, it should be coordinated to the technical person
in-charged, to expedite the resolution of the error.
 Errors encountered during the processing of the report must be corrected. Once the error is
corrected, the Business User can re-run the report manually.

Launch Parameters
Launch parameters for the VC Assets Accountability Report concurrent program include: (refer to
Report Parameters for details)
• Asset Book
• Employee

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 5

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Technical Overview

Considerations
If any Oracle tables change in future versions of Oracle tables, components of this customization
may also require changes to work correctly. Evaluating the impact of such changes on custom
programming is the responsibility of the company, although additional consulting services can be
contracted to assist prior to upgrading.

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 Year 2000 or Y2K support is used. Coding for any future Century
Date is now considered 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.
When designing and building application extensions, it is essential that all dates be entered,
stored, and processed using the full four-digit year for compliance with Century Date standards.
In the case of custom interfaces, both the program code and imported legacy or third-party
application data must be checked for compliance with Century Date standards.

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 6

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only
Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact

Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact

Date

20171205–BL–FIN–BF–MD050 –FA–ISSUE-V2.0 Document ControlDocument Control 7

Error: Reference source not foundError: Reference source not found
Company Confidential - For internal use only