Setting Up and Enriching Data In the Operational Warehouse - Enriched

This chapter discusses how to:

• Set up account information.

• Specify ledger mapping defaults.

• Defining ledger event codes.

• Defining performance ledger templates.

• Define detail ledgers.

• Define ledger groups.

• Define models and scenarios.

• Process roll-ups.

• Set up and run currency conversion for the OWE

Setting Up Account Information

This section provides an overview of account information setup and discusses how to:

• Define account types.

• Define accounts.

• Define account nodes.

Understanding Accounts

Like general ledger accounts, accounts in PeopleSoft EPM hold the key to monetary values stored in ledgers. These values are held in certain buckets—accounts—according to their function.

If you have PeopleSoft General Ledger you can duplicate your general ledger account structure from your transaction system using PeopleTools Data Mover to move your accounts to your PeopleSoft EPM database. If you use another online transaction processing (OLTP) system or a legacy system, you can migrate your structure using data migration tools.

PeopleSoft Performance Management Warehouse contains a couple of important account tables:

Pages Used to Set Up Account Information

Defining Account Types

Access the Account Types page.

Account Type

Displays a letter-code that identifies each account type. You assign account codes to new accounts (those not migrated from other systems) that you enter on the Account page. Values include: A: Asset E: Expense L: Liability Q: Equity R: Revenue F: Force Balancing D: Detail

Balance Forward

Select if you use this account type primarily to determine whether to store balance forward amounts. How you track balance forward amounts is completely up to you. For example, in your regular accounting system, you may want asset, liability, and equity accounts specified as balance forward accounts, but not revenue or expense accounts. The accounts you define later on the Accounts page will take on the balance forward attribute of the account type you assign to them.

Warning! For accounts that you use with PeopleSoft financial services industry applications it is important that you not deviate from the account type codes mentioned here. All asset accounts must be tagged with an A, expense accounts with an E, and so on.

Defining Accounts

Access the Accounts page.

Monetary Account Type	Select from the account types defined on the Account Types page. Note. To obtain account information on reports, you need to add those accounts to the system. In PeopleSoft EPM, you set up a base of general ledger accounts by migrating them from your transaction accounting system. However, when your data migration is complete, you may find that you need to add new accounts to your system. Warning! For accounts that you will use with financial services applications—PeopleSoft Enterprise Funds Transfer Pricing, Risk-Weighted Capital, and Asset Liability Management—it is important that you not deviate from the standard account type codes. All asset accounts must be tagged with an A, expense accounts with an E, and so on.
GL Account	Select if the account is a transaction-based account.
PF Account	Select to make the account available through PeopleSoft Performance Management Warehouse for the performance (PF) ledger.
ABM Account	An account tagged as an ABM account creates more detailed information within the performance (PF) ledger. The ABM-specific fields on this page enable you to specify that the performance ledger contain both the appropriate profitability dimension (cost object), and the activity that contributed costs to the cost object.
Object Type	When you select the ABM Account check box, a drop-down list box for object type appears. Select a default object type for the account.
Activity ID	When you select the ABM Account check box, a drop-down list box for activity ID appears. Select a default activity for the account.
Statistical Account	If you are establishing a statistical account, select the check box and select a unit of measure. Statistical accounts store only statistical amounts, not monetary amounts.
Unit of Measure	If you want to track statistical amounts, select a unit measure.

Warning! Although monetary amounts are assigned to performance (PF) accounts, there is no reconciliation per se, as there is in PeopleSoft General Ledger. The performance (PF) account and source dimensions are used to store and reconcile amount facts to the same amounts stored by a general ledger account. Performance (PF) accounts can differ significantly from general ledger accounts.

Defining Account Nodes

Access the Account Nodes page.

You can define accounts nodes to which you will later assign accounts. The page displays an effective date, status, and description for each node.

Specifying Ledger Mapping Defaults

As a next step you need to specify your ledger and ChartField mapping.

On the Ledger Mapper Defaults pages, you specify the defaults and behavior for the Ledger Mapper page in PeopleSoft Performance Management Warehouse. The defaults you specify here determine how a new row in the Ledger Mapper page is presented and edited. You can override the defaults later on the Ledger Mapper page if you want to set up your mappings differently.

You use the Ledger Mapper to map data, such as assets and liabilities, that does not come into the system through one of the optional analytic applications. The Ledger Mapper is described later in this PeopleBook.

This section discusses how to:

• Specify tree views.

• Specify trees, default values, and validation.

• Set ledger mapping tree usage.

See Also

Setting Up Ledger Mapper

Common Elements Used in This Section

Pages Used to Set Up Ledger Mapper Defaults

Specifying Tree Views

Access the Ledger Mapper Defaults page.

ChartField	The page displays the ChartFields: map from ledger, general ledger account, operating unit, department ID, and product.
Tree View Name	For each ChartField, specify the appropriate tree view name. The prompt displays all views that have Set Control Field as BUSINESS_UNIT and TREE in the name of the view.
Treenode View	For each ChartField, specify the appropriate treenode view name.

Note. If you configure ChartFields of your own to add to the system, you will need to duplicate the tree view, treenode view, and prompts. The system uses the specified views to select members from the trees you specify on the Ledger Mapper Defaults II page.

Specifying Trees, Default Values, and Validation

Access the Ledger Mapper Defaults II page.

Tree Name	For each ChartField including your ledger, select the appropriate tree name from which you'll map values. The tree you select should also represent how your ChartFields roll up for reporting purposes. The tree name is required if you select the Tree check box.
Defaults	Select whether to map all values in the system for the ChartField row or only to those values that are filtered out through the tree and tree views you selected. If you select Tree, the system requires you to enter the tree name.
Validation	To disallow the selection of blank values from prompts and drop-down list boxes for a specific ChartField or for your ledger, select the appropriate validation check box. This validation occurs on saving the Ledger Mapper Defaults component.

Mapping Ledgers to Trees

Access the Map Ledger to Tree page.

To specify whether a tree will be used while mapping the ChartField select the appropriate check box in the Select ChartFields to use trees group box.

Note. This page is used for Performance Management Warehouse general ledger mapping in addition to ABM ledger mapping. This page and the Ledger Mapping Defaults pages should be defined before you create ledger mapping rules.

Defining Ledger Event Codes

Ledger event codes relate performance ledger data so that you can report on the data or compare data between and within engines and models. Ledger event codes also make it possible for the Data Manager and Allocation Manager to assign an account to the target (as defined in the Data Manager or Allocation Manager) for reporting purposes and for posting.

This section discusses how to establish ledger event codes.

Page Used to Set Up Ledger Event Codes

Establishing Ledger Event Codes

Access the Ledger Event Codes page.

Source	Use to specify the data that you will tie to the code. This helps you further filter where the amounts for this code originate. You can select from output that originates in your general ledger or transaction system, or in the various PeopleSoft EPM engines.
Account	Specify the account that you want to assign to the ledger event code.
Account Offset	You can also specify the account offset that you want to assign to the ledger event code.
Model ID	(Optional) Specify a model to associate with the code.
Record	(Optional) Specify a record to associate with the code.

Note. If you use PeopleSoft Enterprise Funds Transfer Pricing or Risk-Weighted Capital, you assign ledger event codes to rules through the Rules pages in those applications. For more information, see the documentation for those applications.

To use ledger event codes appropriately through the Data Manager or Allocation Manager, you need to designate the PF_LEDGER_EVENT_CD field on the TableMap and DataMap system pages.

See Also

Setting Up Tablemaps

Setting Up Datamaps

Using EPM Foundation Data Enhancement Tools

Defining Performance Ledger Templates

This section provides an overview of performance ledger templates and discusses how to:

• Set up a performance ledger template.

• Specify ledger template ChartFields.

• Assign temporary tables to records.

Understanding Performance Ledger Templates

A ledger template defines the physical attributes of a ledger and streamlines the ledger definition process. You define the template once and use it for all your ledgers.

When you create a ledger template, the system automatically identifies the list of ChartFields based on the ledger table selected. The ChartFields are identified based on the following criteria:

ChartField is equal to any field between the ACCOUNTING_PERIOD and CURRENCY_CD fields based on the selected ledger table's structure in the database

The currency code field is also always treated as a ChartField.

PeopleSoft provides a number of predefined ledger templates, which include default records and fields that support the ChartFields and other field and record definitions delivered with the system. (SetID does not key the template). If you want to create a new template or modify a template's records or fields, you need to follow the instructions in this section.

You define performance ledger templates using the Ledger Template component.

Note. The last page in the Ledger Template component, Budget Variables, is used by PeopleSoft Budgeting and is described in that PeopleBook.

See PeopleSoft Enterprise Planning and Budgeting 9.0 PeopleBook

Pages Used to Define Performance Ledger Templates

Setting Up a Performance Ledger Template

Access the Ledger Template page.

Detail	Select this ledger type for ledgers containing detail ledger ChartFields which serve as keys.
Summary	Select this ledger type for ledgers to be used for reporting purposes.
EPM Ledger Type	Unless you're working with PeopleSoft Enterprise Global Consolidations or Planning and Budgeting, you'll select Performance Measurement Ledger. If you change the EPM Ledger Type field, the system resets the values for the ledger records and ChartFields. Your selection here also determines what fields will be displayed on the Detail Ledger page so that the ledger data in the ledger table is uniquely identified. Note. If you select an EPM ledger type of Consolidation Source Ledger, do not select a journal line table name as journal entries for these tables are not supported.
Used in Consolidations	Select this check box if this ledger template is used for consolidate information for reporting.
Ledger Record	Represents the ledger record that you use to store the balances for each ChartField combination that has posted activity.
Journal Line	Stores detail lines containing the monetary and statistical amounts for each journal entry.

Note. The ledger record and journal line prompts are based on PeopleSoft EPM record metadata. If your desired table is not returned in the prompt, define it in your PeopleSoft EPM record metadata first.

You can access the Record Metadata page for the ledger record or journal line currently selected directly from the Ledger Template page by selecting the link beside the Ledger Record and Journal Line fields. The link text varies based on the ledger record or journal line selected. In the example above, in the Ledger Record field, select the Performance Ledger link to access the Record Metadata page for the ALM_LEDGER_F00 performance ledger.

See Also

Setting Up Record Metadata

Specifying Ledger Template ChartFields

Access the Ledger Template - ChartFields page.

Select Edit Table and View - No Effective Date records to use for this template.

The page accesses a set of default edit table names and reporting views for the ChartFields in the ledger. The edit table value comes from the edit table specified in the Application Designer for this field on the ledger table. The View - No Effective Date field is used for reporting prompts when you do not want to limit the selection by effective date (because historical rows might contain ChartFields that are no longer active). You can change these values if you are modifying your system.

Assigning Temporary Tables to Records

Access the Ledger Template - Edit and Post Variables page.

Temp Table 1 Name, Temp Table 2 Name, Temp Table 3 Name, and Temp Table 4 Name	Use to assign up to four temporary tables to the ledger template. Your temporary table selection must match those tables in your ledger template. Each of the four temporary tables represent the journal and ledger records that Profit Manger uses to process your ledgers and journals.
Run Edit for Profit Manager	Select this check box to run edit for the Profit Manager.

Note. The journal and ledger tables have ChartField subrecords. If you add ChartFields, you must modify these table subrecords

See Also

Processing and Posting Journals

Defining Detail Ledgers

Use the Detail Ledger component to link a ledger template to a detail ledger and specify the balancing options for the journals generated to a detail ledger.

Note. The second page in the Detail Ledger component, Consolidations, is used by PeopleSoft Enterprise Global Consolidations and is described in that PeopleBook.

See PeopleSoft Enterprise Global Consolidations 9.0 PeopleBook.

Page Used to Define Detail Ledgers

Specifying Detail Ledgers

Access the Detail Ledger - Definition page.

Ledger Template	Select the ledger template to link to this detail ledger. Click the link that displays alongside the ledger template you select to access the Ledger Template page for that template.
EPM Ledger Type	Displays the type of ledger selected in the Ledger Template field.
Ledger	Displays for a ledger type of standard general ledger, budget project ledger, commitment budget ledger.
Budgeting Scenario	Displays for a ledger type of budget project ledger and commitment budget ledger.
Scenario ID	Displays for a ledger type of performance measurement ledger and consolidation ledger. Select the scenario ID to use.

Defining Ledger Groups

Ledger groups enable you to group detail ledgers by ledger template and ledger type.

This section discusses how to set up ledger groups.

Page Used to Define Ledger Groups

Setting Up Ledger Groups

Access the EPM Ledger Group page.

Ledger Template

Select a ledger template from the drop-down list box. Ledger templates are defined on the Ledger Template pages. Click the link alongside the Ledger Template field to transfer to the Ledger Template Definition page for the selected template.

Ledger Group Type

Select a group type from the following: Average Daily Balance: Allows only a primary ledger. Budget: Allows only a primary ledger. Commitment Control Expense: Used by commitment control budgeting. Commitment Control Revenue: Used by commitment control budgeting. Standard: Allows one primary and up to nine secondary ledgers. Translation: Allows only a primary ledger. See PeopleSoft Enterprise Planning and Budgeting 9.0 PeopleBook

Entering Ledger Details

The Ledger Details grid at the bottom of the page displays two tabs: Types and Attributes.

On the Types tab select the following:

On the Attributes tab select the following:

Note. If you're setting up a commitment control ledger group, two additional fields display: the Commitment Control Ledger Type field and the Affect Spending Authority field. These fields are specifically for commitment control purposes.

Defining Models and Scenarios

This section provides an overview of models and scenarios and discusses how to:

• Create model definitions.

• Set up historical scenarios.

• Enter historical scenario business rules.

• Enter historical scenario economic assumptions.

• Set up forecast scenarios.

• Enter forecast scenario business rules.

• Enter forecast scenario economic assumptions.

• Assign scenarios to business units.

Understanding Models and Scenarios

Models enable you to define how to measure performance within your organization and the types of data that you want to review through various reports. For example, you may want to review revenue information on a region-by-region basis—a very high-level scope. Or, you may want to review only those activities that relate to a certain product line for certain types of resources—a very narrow scope. Each analytical application uses models and scenarios differently.

Regardless of the size or scope of your model, you must initially proceed with the same set of steps. Likewise, when you set up models you perform setup steps that are common to all products in the PeopleSoft EPM product line. However, how you complete the process depends on which EPM products you license.

Note. You should refer to your application-specific PeopleBook for more information on models and scenarios in your product.

Modeling Terminology

When using models, you should familiarize yourself with the following terms:

• Parent model: The master model that is used as the basis for an impact study.

• Child model: A child model stores the changes to the master or parent model.

  The child model inherits all the properties from the parent model.

• Scenario: You create a scenario ID for each parent and child model that you want to study.

  This scenario ID is used on all run controls.

Object-Based Modeling

Object-based modeling enables you to simulate various changes in an organizational model and study the impact on costs, revenue, and profitability. Instead of copying the whole model, you can copy only the data that needs to be changed. This reduces the volume of data copied and helps to identify the changes made and any effects the changes may have. Object-based modeling helps to define just the changes for the child model. All the unchanged data for the child model is inherited from the parent model. Enhanced modeling features improve the maintenance, reusability, and flexibility of a model, enabling you to create parent and child models easily.

Object-based modeling can be used not only in PeopleSoft Activity-Based Management but also in other applications in PeopleSoft EPM so that you can use your system to do planning and simulation. Scenarios for planning and simulation can be defined as child models. Child models represent the business decisions and assumptions for the scenarios. Scenarios can be simulated for each child model using various forecast distributions for a given timespan. Results for various scenarios can be compared to select the best case scenario.

Scenarios

Once you establish warehouse business units and setIDs, you create model IDs (where you define the parent and child relationships) and then point to those model ID by means of a scenario ID. Scenarios:

• Serve as a wrapper to run all analytic models.

  When you run the analytical application engines, the engines tie the models together by means of the scenario ID.

• Enable you to work with what-if scenarios by creating more than one scenario with different models attached for what-if comparisons.

There are two types of scenarios:

• Historical.

• Forecast.

To set up scenarios:

1. Complete the Scenario Definition page.

2. Select the type of scenario (historical or forecast) and complete the appropriate pages.

3. Specify the rates that you want to use on the Economic Assumptions page.

4. Assign the scenarios to a business unit using the PF Unit Scenario Definition page.

Pages Used to Define Models and Scenarios

Creating Model Definitions

Access the Models page.

Parent Model ID

For a child model that rolls up to another model, specify that ID of the parent model in this field.

Setting Up Historical Scenarios

Access the Scenarios - Definition page.

Input Scenario ID	By default, the input scenario ID is the same as the scenario ID. When you run a jobstream, Resolver uses the input scenario ID associated with the run control scenario ID to select data from a scenario-keyed table. This way, you can access data from a scenario other than the one you provide at run time.
Scenario Type	Select a scenario type of Historical. The component displays the Historical Business Rules tab. Note. Depending on the scenario type you select, certain fields appear and others are hidden on all tabs within this component.
Consolidated	Select this check box to identify this scenario as one to which other scenarios will roll up.

Entering Historical Scenario Business Rules

Access the Scenarios - Historical Business Rules page.

Default Model ID	If you specify a default model ID, then the rest of the models listed default to that ID. Otherwise you can select specific models for the various applications
ABM Model	Model ID to use for your PeopleSoft Activity-Based Management application.
FIN Model	Model ID to use for financial analytics.
Workforce Analytics	Model ID to use for your Workforce Analytics applications.
KPI Model	Model ID to use for Key Performance Indications and scorecards.
GLMP Model	Model ID for the ledger mapper.
CRM Model	Model ID to use for your CRM analytics applications.
Console Model	Model ID to use for consolidations.

Entering Historical Scenario Economic Assumptions

Access the Scenarios - Economic Assumptions page.

Rate Type

Select from the following: Market Rates: Use current interest rate information. Deterministic Rates: Enables you to select a hypothetical interest rate environment previously created within PeopleSoft Asset Liability Management. Deterministic rates play an integral role in modeling a financial services institution's exposure to interest rate risk. They enable you to model dynamic interest rate environments explicitly. If you define a scenario with either a deterministic rate assumption or a stochastic one, then you must select the term structure model ID to accompany the scenario. Stochastic Rates: Scenarios with this rate type are used to randomly generate interest rate scenarios, and they are used in risk management. If define a scenario with either a deterministic rate assumption or a stochastic one, then you must select the term structure ID to accompany the scenario. Age-Graded Table: Used for PeopleSoft Enterprise Workforce Analytics. The age-graded table includes effective dates of rate and rating factors (such as age ranges, sex, and smoking status) by employer and employee. The arrays of values used to calculate the cost of a plan to an employee. Rates can be age-graded, service-related, or general, depending upon the benefit plan type. Flat Rate Table: Contains information on where you define rates to be charged per selected frequency for a particular benefit program or plan. The Flat Rate table represents a constant value. For all subsequent years, as well as the first time it is done, flat rate is calculated simply by applying the flat rate percentage to the average balance and allocating this amount among the periods. Salary Percent Table: Used in PeopleSoft Enterprise Planning and Budgeting, this table contains information related to earnings as a percentage of the base or gross salary amount. Service Rate Table: Used in PeopleSoft Enterprise Workforce Analytics, this table stores information such as service rate ID, effective date, pay frequency, rate per unit, service intervals, total rate, employer portion, and employee portion. Service rates are employee related rates. For example, a service rate would be an employee's days of vacation accrued per year or per month for a given vacation plan.

Note. You create term structure model IDs as part of your setup for using PeopleSoft FSI applications.

Setting Up Forecast Scenarios

Access the Scenarios - Definition page.

Entering Forecast Scenario Business Rules

Access the Scenarios - Forecast Business Rules page.

Specify the model IDs you want to use for each year and period. The selections you make depend on the analytic applications you have installed.

Note. You must specify a prior scenario ID on the Scenario Definition page to select a model of Financial Statement Simulator.

Entering Forecast Scenario Economic Assumptions

Access the Scenarios - Economic Assumptions page.

The fields on this page are the same as those discussed for the Historical Forecast - Economic Assumptions page.

Assigning Scenarios to Warehouse Business Units

Access the Warehouse Business Unit Scenario Definition page.

Scenario ID	For each business unit, select the appropriate scenario ID.
Calendar ID	For each business unit, select the appropriate calendar ID. Note. There is a relationship between the calendar ID on this page and the calendar ID on the Scenario Definition page. If you make an entry on this page that associates a calendar ID to a scenario and business unit combination, you can no longer change the calendar ID on the Scenario Definition page (the field is disabled).
Manual Journal Approval	Journal approvals allow specific requirements to be met before the approval is finalized. The system defaults to Pre-Approved for the Manual Journal Approval option. The Approval Required - Security and Approval Required - Workflow options are used by PeopleSoft Enterprise Global Consolidations.
Business Process Name	If you are using the approval workflow option in PeopleSoft Enterprise Global Consolidations, specify the business process name for the approval workflow.
Approval Rule Set	If you are using the approval workflow option in PeopleSoft Enterprise Global Consolidations, specify the approval rule set to be used for the selected business process.

See PeopleSoft Enterprise Global Consolidations 9.0 PeopleBook.

Processing Roll-Ups in the OWE

This section provides an overview of EPM Foundation roll-up engines, lists common elements, and discusses how to:

• Roll up scenarios.

• Roll up calendars.

• Roll up business units.

Understanding EPM Foundation Roll-Up Engines

In the PeopleSoft Performance Management Warehouse, you can run calendar roll-ups on the application data, the performance ledger table (PF_LEDGER_F00), and roll up ledgers on the GL ledger table. In addition you can roll up scenario IDs and business units. Running the roll-up engines enables you to present the same information in a different (aggregated) way.

You can use the calendar roll-ups to roll up accounting periods based on the summary and detail calendars that you defined for your scenario. Most likely, you will use a calendar roll-up before you report on your scenario. For example, you may have monthly values in your current scenario data, but want to see quarterly values.

You can use the scenario ID and business unit roll-up engines to consolidate values. For example, when you define warehouse business units, you may specify that several business units roll up under a consolidated business unit. When you then run the business unit roll-up, the individual business unit data is aggregated into the consolidated business unit and can be reported in that way.

Note. Although the roll-up engines are usually the only job in a jobstream, they must still be set up in a jobstream. No merge is required on this engine.

Common Elements Used in This Section

Pages Used to Run Roll-Up Engines

Rolling Up Scenarios

Access the Roll-Up Scenario page.

Business Unit, Scenario ID, Fiscal Year, and Accounting Period	Enter the business unit, scenario ID, fiscal year, and accounting period for the roll-up.
Tree ID	You can select a tree. Ensure that the tree you select contains a setID.
Job ID	Select SCN_ROLL.
ABM	Select this check box to roll up the scenarios in the tables associated with PeopleSoft Enterprise Activity-Based Management AB_JOB_CD_F00, CALC_DETAIL_F00, and CALC_OBJ_F00 tables.
BSC	Select this check box to roll up the scenarios in the tables associated with PeopleSoft Enterprise Scorecard KP_DATAVALS_F00 table.
PF Ledger	Select this check box to roll up to the PF_LEDGER_F00 table.

Click Run to run this request.

Rolling Up Calendars

Access the Roll-Up Calendar page.

Business Unit, From Scenario ID, Scenario ID, Fiscal Year and Period	Enter the business unit, from scenario ID, scenario ID, fiscal year, and accounting period for the roll-up.
Job ID	Select LED_ROLL.
ABM	Select this check box to roll up the calendars for PeopleSoft Enterprise ABM.
PF Ledger	Select this check box to roll up performance ledger calendars.

Click Run to run this request.

Rolling Up Business Units

Access the Roll-Up Business Unit page.

Business Unit, Scenario ID, Fiscal Year and Accounting Period	Enter the business unit, scenario ID, fiscal year, and accounting period for the roll-up.
Tree ID	You can select a tree. Ensure that the tree you select contains a setID
Job ID	Select BU_ROLL.
ABM	Select this check box to roll up the business units for PeopleSoft Enterprise ABM.
BSC	Select this check box to roll up the business units associated with PeopleSoft Enterprise Scorecard.
PF Ledger	Select this check box to roll up business units for PF ledger.

Click Run to run this request.

Setting Up and Running Currency Conversion for the OWE

This section provides an overview of currency conversion process for the OWE and discusses how to:

• Define currency conversion rules.

• Create currency conversion rule sets.

• Associate a conversion rule set with a job.

• Run currency conversion.

• Review multicurrency conversion messages.

See Understanding EPM Multiple Currency Management.

Understanding Currency Conversion for the OWE

In PeopleSoft EPM, you can obtain profitability figures that include the effects of multiple currencies. The economic effects of transactions can be reconciled with accounting effects with greater accuracy. In addition, the effect of currency fluctuations (when analyzing similar business units or processes in different countries) is eliminated.

While data may be brought into EPM in many different currencies, the amounts must be converted to a single currency for each business unit in order for proper engine processing to occur. PeopleSoft EPM engines use these converted base amounts as input and output base amounts from their processes.

The Currency Conversion application engine can be used on any fact table containing the from and to currency code fields and the from and to amount fields (for example the FI_INSTR_F00 or REVENUE_F00 tables).

The Currency Conversion engine enables you to perform conversion on any fact table. However, only temporary tables defined for the fact tables are updated by the conversion engine. The Currency Conversion process should be run between two other jobs. For instance, run a job that populates the temporary table for the fact table, followed by the Currency Conversion engine process to update the temporary table, and then a job following the conversion that updates the actual fact table using the results from the temporary table.

Reports specific to currency processing are not included with PeopleSoft EPM. To view reports in a reporting currency other than your base currency, build a data mart from the PF_LEDGER_F00 table, migrate the selected data to the data mart, and run currency conversion on the data mart.

The Currency Conversion engine can be run either as a job within a jobstream, or it can be called as a function library from another PeopleSoft EPM engine.

Note. Because all ledger accounts, regardless of the engine processes, must go through the PF_JRNL_F00 before the edit and post process in order to populate to the PF_LEDGER_F00, all conversions for ledger accounts must be done on the PF_JRNL_F00 table (rather than directly on the LEDGER or PF_LEDGER tables).

Note. Any desired conversion on the LEDGER table (prior to the PeopleSoft Activity-Based Management engine using base amounts as input) must be done by the delivered ETL tool or by a configured solution created at implementation time.

Delivered Multicurrency Metadata

This table lists delivered multicurrency tablemaps, datamaps, and associated primary record names:

Prerequisites

Before creating currency conversion rules and rule sets, and associating them with jobs, you must:

• Set up your currency metadata.

• Set up jobs with which you want to run OWE currency conversion.

See Also

Setting Up and Working with EPM Foundation Metadata

Setting Up Job Metadata

Pages Used to Set Up and Run OWE Currency Conversion

Describing Currency Conversion Rules

Access the Currency Conversion Rule page.

Rate Type	Select the exchange rate type to use for this rule. The type that you specify overrides any rate type specified by the business unit. If you don't select a rate type, the system uses the rate type specified for the business unit.
As of Dated	Select to use the as of date. If you do not select this check box, the system uses the period end date (based on the jobstream run parameters) as the effective date for the exchange rate. If you select this check box, any job running with this currency conversion rule uses the as of date to determine the exchange rate.
Constraint Code	Specify a constraint code. Constraints are defined using the Constraint component.
From Currency Code Column	Select the appropriate column from your constraint code. Any field that is not defined in the constraint as a measure is a valid value.
To Currency Code Column	Select the appropriate column from your constraint code. Any field that is not defined in the constraint as a measure is a valid value.
From Amount Column	Select the appropriate column. Any field defined in the constraint as a measure, and that has 1 ? 3 decimal places, is a valid value.
To Amount Column	Select the appropriate column. Any field defined in the constraint as a measure, and that has 1 ? 3 decimal places, is a valid value. Note. If your amount columns have more than four decimal places, you must define a view for this table to redefine your amount fields. You then use this view to build your metadata and ultimately the constraint that is used as input to the multicurrency rule.

You can add more rows. You must enter field names for at least one from and one to currency code and at least one from and one to amount column. You can enter multiple from and to amount column field names for constraints that contain multiple amount fields, such as the Instrument table (FI_INSTR_F00). After you have set up currency conversion rules, you can create a conversion rule set.

Note. For each rule that you create, you must establish multicurrency tablemaps (identified as target tables), multicurrency datamaps (with amounts specified as measures), and multicurrency constraints. PeopleSoft EPM is delivered with standard table and datamaps for multicurrency. They can be identified by the MC_ prefix.

Creating Currency Conversion Rule Sets

Access the Currency Conversion Rule Set page.

Expense Sequence Number	Enter a number to control the order in which the Currency Conversion engine runs your rules. To accommodate the addition of future currency rules, use numbers such as 100, 200, 300.
Currency Rule Code	Select the name of the rule that you created.

Note. Each currency rule must be in a rule set. You can also use the rule set to combine multiple currency rules.

After you have set up the currency conversion rule set, you need to associate the rule set with a job.

Associating a Conversion Rule Set with a Job

Access the Job Conversion Rule Set page.

Job ID	Enter the job with which you want to associate this rule set. You create jobs on the Job Metadata page. When you run this job in a jobstream, the system processes the currency conversion rules based on the rule set associated with the job.
Currency Rule Set	Select the rule set that you created. After you have created a job rule set, you can run the Currency Conversion engine using the rules you have set up.

Note. A currency conversion rule set can be assigned to more than one job, but each job can contain only one currency conversion rule set.

Running the OWE Currency Conversion Process

After you have completed this setup and set up your jobstreams, the Currency Conversion engine runs as part of the jobs that you defined. The engine ensures that all transactions are coded with the information that the system needs to manage multiple currency transactions. The timing of running the Currency Conversion process varies based on your business processes and the PeopleSoft EPM engines involved in your processes. Because most engines use the base currency amounts in their calculations, you must run the Currency Conversion process prior to the other engine processes for the proper base currency amounts to be available for engine processing.

The Currency Conversion engine affects any record in the warehouse that contains currency code and amount fields.

See Also

Delivered Multicurrency Metadata

Reviewing Multicurrency Conversion Messages

Access the Message Header and Message Detail pages.

Note. These pages are described in the “Streamlining Processing with Jobstreams” chapter.

Consider the following when you review dependencies:

• All amount fields for a record must be migrated to the warehouse in a single currency.

  For example, you cannot have instrument balance in USD and payment amounts in MXP.

• Multicurrency tablemaps must be designated as target tablemaps.

• Multicurrency datamaps must use the multicurrency tablemaps.

• Amount fields on multicurrency datamaps must be designated as measures, because the prompt table for these amount fields on the rule page uses a view that filters out anything that is not designated as a measure.

• Any constraints used on the rules must be specific to the multicurrency datamaps.

• Jobs that are to be run using the Currency Conversion engine must have one conversion rule set defined, and each rule set must contain at least one rule.

See Also

Viewing Engine Messages