l07 entities scenarios

7Copyright © 2008, Oracle. All rights reserved.

Setting Up Entities, Calendars, and Scenarios

Copyright © 2008, Oracle. All rights reserved.

Objectives

After completing this lesson, you should be able to:

• Set up entities

• Set up calendars

• Set up scenarios


Setting Up Entities

Entity

[None]

Activity

California

UnitedStates

Geographical

Plant1

WestSales

Connecticut

EastSales

Entity

[None]

Activity

Geographical

SalesServices

WestSales

Manufacturing

EastSales

EmeaSales

EmeaService

Development

EastSales and WestSales occur in alternate rollups.


Requirements for Entities

Before adding an entity, you should have this information:

• The parent to which the entity’s data rolls up

• The input currency for the entity

• Whether adjustments through journal should be allowed for the entity

• The security class for the entity

• Whether the entity can be a partner in intercompany transactions

• For statutory applications, the holding company for the entity


Entities and Journals

• The AllowAdj property enables posting of journal adjustments to the Ent Curr Adjs member for an entity.

• The AllowAdjFromChildren property enables posting of journal adjustments to the Parent Adjustment and Contribution Adjustment nodes of the Value dimension.


Entities and Intercompany Partners

Specifies whether the entity is displayed as a member in the ICP dimension

Specifies a security class for the entity for intercompany transactions


Entities and the ICP Dimension

The ICP dimension includes all members of the Entity dimension for which the IsICP property is selected.

California

Plant1

West Sales

1000

Members of the ICP dimensionMembers of the Entity dimension

IsICP member attribute selected

Plant1

West Sales


Adding Currencies

• Every Financial Management application must include a currency dimension.

• The currency dimension must include a currency for each default currency assigned to an entity in the Entity dimension.

Currency members


Setting Up Calendars

• The Financial Management calendar is defined by the year, period, and view dimensions.

• You can customize the start year, number of years, base periods, summary periods, and period-to-date views.

• You cannot modify the calendar dimensions for an application after it is deployed.


Setting Up Scenarios

• The Scenario dimension represents a set of related data, such as budget, actual, or forecast.

• Information for scenarios:– Data frequency– Default data view, periodic or year-to-date– Periodic or YTD consolidation– Process management options– Enable or disable line-item detail– Enable or disable data audit


Frequency and View

• The frequency of a scenario specifies the time period level at which data can be input; for example, months or quarters.

• The default data view for a scenario can be either periodic values or year-to-date values.

January February March Quarter 1

Periodic 10 10 15 35

Year to Date 10 20 35 35

Year to Date givesa running total.


View and Missing Data

• Missing data can be interpreted as either zero for the current period (Periodic) or as zero for year to date (YTD).

• You can specify separate settings for nonadjusted data and for adjusted data.

Data for February is missing.Budget scenario uses ZeroView=Periodic.

Forecast scenario uses ZeroView=YTD.


Scenarios and Process Control

Process Control is enabled by scenario.


Summary

In this lesson, you should have learned to:

• Set up entities

• Set up calendars

• Set up scenarios

l07 entities scenarios

Documents

entities entity

scenario dimension

currency dimension

missing data missing

set of related data

nonadjusted data

entitys data

data audit