Professional Documents
Culture Documents
Implementation
Author:
sonam kumari
Email :
slashsonam@gmail.com
Contents:
1.
2.
3.
4.
5.
Project
Creation
from
Budget
Creation
Expenditure
Creation
Transferring
Assets to FA
Set Up Required:
Setup 6.2, 6.3, 6.4,
5.5, 6.6, 6.8, 5.9
Set Up Required:
Setup 6.7
Set Up Required:
Setup 6.10, 6.11
Depreciatio
n in FA
Reports
Generation
batch name, expenditure class and expenditure ending date. In SAS all the
expenditures are entered under miscellaneous expenditure class as auto
accounting is set for this class. Now for entering expenditure first an expenditure
organization is selected from organization LOV. This LOV lists all the expenditure
owning organizations which are part of the expenditure hierarchy associated to
US OU as part of implementation option setup. Secondly project number, task,
expenditure type and quantity is selected and at the same time expenditure DFF
is also supplied with appropriate values of LE, BU, Department, and account for
accounting. Project number field will allow all projects except in cancelled, closed
and Recovered status to be entered. Task field will accept all chargeable child
level tasks associated to project. Expenditure type will list out all the expenditure
type associated to miscellaneous expenditure class. Quantity is entered based
on which raw cost would be calculated at the time of distributing cost. Raw cost
will product of quantity and rate. Rate is set for each expenditure type at the
time of expenditure type definition. If no rate is defined it is considered to be
one. After entering all the expenditure for a particular batch it s submitted and
released for processing.
To process an expenditure batch a series of standard programs are submitted.
PRC Distribute Usage and Miscellaneous Cost:
This process
computes the costs and determines the GL account to which to cost
must be posted.
PRC generate cost accounting events
Create accounting
PRC update Project summary amounts
4. Capitalization: It is the method of transferring asset from oracle projects to
fixed assets. Book becomes an asset to SAS when it gets published. For
publishing a book
Status of the project(book in SAS) is changed to published
Cost of asset is calculated based on expenditure created for all capitalized
task associated to project. Total cost of asset reflects in CIP field of the
capitalization screen after successful completion of PRC update project
summary amounts. This cost will be the cost of asset reflecting in FA.
Asset type is changed form Estimated to As-Built and Actual in service
date is also supplied. All mandatory asset information is filled if not filled
earlier at the time of asset creation.
MX OU
HE
MX_SAS
SP OU
SP_SAS
IT OU
IT_SAS
Prof.
SC
CTB
ELS
SAS
Company has its business in 4 different geographies (Italy, Mexico, Spain, US)
so it have 4 different operating units.US OU have 5 different organizations (HE,
SG, Prof, CTB, ESL) which hold projects and an organization (SAS) to hold all
the events/expenditure associated to these organizations. Similarly for Italy,
Mexico, Spain, Colombia OU event/expenditure org are SAS_IT, SAS_MX,
SAS_SP, and SAS_CO respectively. For each Operating unit one organization
hierarchy is defined. It starts from corresponding OU and having all the
subordinate are at the same level in a particular hierarchy.
4. Implementation option: This form is used to relate operating unit to the
corresponding
ledger, business group, currency, calendar project and
expenditure related setup. In projects/expenditure tab a unique organization
hierarchy (as defined in step 3) is assigned to each operating unit.
Organizations in these hierarchies will be populated for project organizations
and expenditure LOV while creating project and expenditure respectively for a
particular operating unit.
5. Classificaion: This form help to define the characteristics used to
differentiate between the projects. They are department, Division, PU,
copyright year, Legal Entity, Attribute. These attribute are entered when new
projects are defined in the system.
6. Service Type: This category is used to segregate
type of task.
Permissible values are (Prepub, Can, WRO, OVS, LATE, Reorg, CIP, MGF)
7. Budget Entry Method: This defines the way how budget would be
entered for a particular project. Here only raw cost for lowest level task is
entered.
8. Project Types: Oracle broadly divides projects in 3 different types, namely
Capital, Contract, Indirect project. Capital project are those projects which an
organization develops for internal use and after completion it could be
considered as an asset eg. (Construction of building). Contract project are
those which an organization does for another company as service and in turn
would generate revenue (Any project which Wipro does for a particular org.).
Indirect project are used to aggregate the overhead cost. Oracle provides the
facility to create any number of project type belonging to any of the above
three classes. New project type will have features defined by the class to
which it belongs. While defining project types, information for Costing,
Budgeting, Capitalization, Classification, Workflow etc. are specified.
Here Capital project is taken into consideration as book is an asset
to SAS. Each OU (US, MX, IT, SP, CO) will hold one capital project under the
project type name as (Prepub) .SAS Company is not dealing in burden cost, so
the costing tab will not have any setup information. Entry method for raw cost
at lowest level task is assigned as budget entry method in budget option tab.
All the Classification (BU, PU, Department, Copyright year, Attribute) are made
compulsory for defining a particular project in classification tab. Capitalized
information is entered to have asset information associated to every project in
the capitalization information tab. A new project created must have Active
status is set in the project status/workflow tab.
9. Project Template: It is a repository of initial setup done for project
creation. It has everything defined in it (Organization, Type, Work break down
structure, Quick entry fields etc.).This is required so that user might not enter
all the information each time new project is created. Once project is created
from template necessary changes can be done.
In SAS one template is created for each and every
organization .As in US OU 5 different organization (HE, SC, Professional, CTB,
ESL) are present 5 templates are created. All 5 template mandates entry of
classification (Project name, Number, BU, Department, PU, Attribute, Copyright
year). Further 4 another template for other OUs (Italy, Mexico, Spain, and
Colombia).
Conversion
UNASSIGNED
Currenc
y
ABC Vendors
Currenc
y
Name
Expenditure
Category
Revenue
Category
UOM
Vendor Services
Currenc
y
MSS Vendors
Currenc
y
Miscellaneous
Costs
UNASSIGNED
Miscellaneous Costs
Currenc
y
UNASSIGNED
Project Worker
Miscellaneous
Costs
Currenc
y
Name
Descrip
tion
Effective
Date
From
Conversio
n
01-Jan2000
Miscellaneou
s
Transaction
01-Jan2000
ABC
Vendors
01-Jan2000
Supplier
Invoice
01-Jan2000
Vendor
Services
01-Jan2000
Supplier
Invoice
01-Jan2000
Miscellane
ous Costs
01-Jan2000
Miscellaneou
s
Transaction
01-Jan2000
MSS
Vendors
01-Jan2000
Supplier
Invoice
01-Jan2000
Project
Worker
01-Jan2000
Miscellaneou
s
Transaction
01-Jan2000
Effect
ive
Date
To
11. Auto accounting: Any transaction that is created in oracle projects need to
be accounted. It aims at determining the correct account for each transaction.
Oracle project creates the accounting events and creates accounting for the
events for the Sub ledger Accounting .Oracle provides predefined rules for SLA
which accepts default account for auto accounting without change. These sub
ledger accounting rules can be modified as per the implementation
requirements.
value based on some input parameter. Various input parameter can serve as the
feed to SQL statement (Class codes, Expenditure ID, Expenditure Type, Project
Type, Project ID etc.) .Intermediate value can be a constant also. Once
intermediate value is known, it may be either mapped to auto accounting lookup
defined or can itself be the segment value.
Various rules defined are like
Rule Name
0-LE from Exp Item DFF
Description
Intermediate Value
Sour SQL Statement
ce
Valu
e
select
ATTRIBUTE1
from
Expenditure_item_ID = :1
Segment Value
Source
PA_EXPENDITURE_ITEMS_ALL
where
Intermediate Value
Lookup Set
Rule Parameters
Sequenc Parameter
e
1
Expenditure
Item ID
Description
Internal ID of Expenditure
Item
2.
Rule Name
Description
Intermediate Value
Sour SQL Statement
ce
Valu
e
select
ATTRIBUTE2
from
Expenditure_item_ID = :1
Segment Value
Source
PA_EXPENDITURE_ITEMS_ALL
Intermediate Value
where
Lookup Set
Rule Parameters
Sequenc Parameter
e
1
Expenditure
Item ID
Description
Internal ID of Expenditure
Item
SAS_US_USD_CORP_OU
Description
Function Transactions1.
Name
Description
Enable
d
Capital,
All
Checked
Segment Name
Rule Name
Legal Entity
Division
Department
Account
Intercompany
4-Intercompany 0000
Future Use 1
5-Future1
Future Use 2
6-Future2
Function 2
Name
Operating
Unit
SAS_US_USD_CORP_OU
Description
Function Transactions.
Name
Description
Enabl
ed
All
Misc
Transactions
Clearing
account
Transaction Costs
for
all
Miscellaneous
Segment Name
Rule Name
Legal Entity
Division
Department
Account
Intercompany
Future Use 1
5-Future1
Future Use 2
6-Future2
Checke
d