Setting Up EPM Foundation

This chapter provides overviews of PeopleSoft EPM Foundation setups and multiple currency setup and processing, and discusses how to:

• Review installed products.

• View charts and print results.

• Specify your EPM sources.

• Set up country and state information.

• Set up time zones.

• Define account calendars.

• Set up the Gregorian calendar for the Performance Management Warehouse.

• Define operator defaults.

• Define units of measure.

• Set up multilanguage processing.

• Set up currency tables.

• Set up market rates.

• Define currency quotations.

• Establish market rates.

• Calculate currency rates.

• Configure currency precision.

• Set up and run currency conversion for EPM Analytical Applications.

• Set up and run currency conversion for the Performance Management Warehouse.

Understanding PeopleSoft EPM Foundation Setups

After installing your EPM product, you must set up key business rules and processing variables for the system. These rules provide the foundation on which EPM Foundation operates and can include country and state, unit of measure, language, and currency information. Because these rules act as a foundation and span the entire EPM product suite, you must perform these setup tasks prior to beginning other EPM activities documented in this guide.

The business rules and processing variables that you define for EPM are stored in EPM database tables. You define these rules and populate the EPM tables using the PeopleSoft Pure Internet Architecture pages in the EPM Setup menu. These pages are built over EPM tables that are shared among many PeopleSoft applications.

You set up the following business rules and processing variables in this chapter:

• Installed products

• Chart viewing and printing

• EPM sources

• Country and state

• Time zone

• Multiple language

• Accounting calendars

• Operator defaults

• Unit of measure (UOM)

• Multiple currency

Understanding Multiple Currency Setup and Processing

This section discusses:

• Multiple currency management.

• Currency and calculation types.

• Revaluation.

• Currency precision.

• Currency as a ChartField.

• Currency Conversion application engine (PF_MULT_CURR) for Analytical Applications.

Multiple Currency Management

PeopleSoft enables you to manage financial information in multiple currencies. PeopleSoft provides specific input, processing, and reporting features that support the European Common Currency (euro), currency conversions, remeasurement, revaluation, translation, and a complete audit trail of all multicurrency processing.

You can define and maintain tables that describe currency codes, exchange rates, market rates, and currency rate types. All PeopleSoft applications use the same market rate and currency pages and tables, which enables you to administer centralized currency controls throughout the integrated product lines.

Before you begin to process multiple currencies, you must understand how foreign currency processing works in PeopleSoft applications and how to set up your system for multiple currencies.

Note. Multiple currency setup steps can vary depending on whether you are implementing PeopleSoft analytical applications or Performance Management Warehouse. Some setup steps are application or warehouse specific, and are required only for that product suite. These setup steps are clearly labeled with Analytical Applications or Performance Management Warehouse to indicate the product suite to which it belongs.

Currency and Calculation Types

PeopleSoft software uses terminology associated with currency that is consistent with generally accepted accounting principles and the Financial Accounting Standards Board (FASB) accounting standards.

Currency refers to the denomination of a monetary transaction. PeopleSoft applications use a currency code (CURRENCY_CD) to identify and track individual currencies. Although the system does not require it, you should use International Standards Organization (ISO) currency codes. PeopleSoft applications have no limit on the number of currencies that you can use.

Important currency terms are:

Important currency calculation types are:

Revaluation

When you adjust the base currency value of balance sheet accounts that are maintained in a foreign currency, this is called revaluation. You generally perform revaluations at the end of each accounting period to reflect the actual base currency value of assets and liabilities as exchange rates fluctuate between the base and foreign currencies. You make adjusting entries to the accounts that are being revalued with an offsetting entry to a revaluation gain or loss account. The gain or loss account is sometimes referred to as an unrealized exchanged gain or loss.

Multicurrency calculations

In this example, a London-based subsidiary of a Swiss company records a purchase made in Mexican pesos. The Swiss company is owned by a United States corporation. The following table correlates the terminology and the currencies:

Currency Precision

Currency dictates the precision of monetary amounts. For example, United States dollar amounts have two digits to the right of the decimal and Japanese yen have none. The system addresses currency precision as follows:

• PeopleSoft software provides currency-sensitive amount fields with a standard length of 23.3, or 23 digits to the left of the decimal point and 3 digits to the right of the decimal point.

• By default, the system rounds all currency-sensitive amount fields to the currency precision of the associated currency. This action is a PeopleSoft PeopleTools option that you can deactivate.

• All numbers on SQR reports are currency-sensitive. For reporting with Crystal and PS/nVision, the display is equal to the field precision, but you can increase the number of decimal places.

Currency as a ChartField

You get the best results when you record multicurrency transactions with a currency ChartField. This approach enables you to record multiple currencies in the same ledger and reinforces the concept of a ledger's role as a record for an entire category of information (such as actuals, budgets, forecasts, or commitments).

Currency Conversion Application Engine for Analytical Applications

While data may be brought into the PeopleSoft Performance Management Warehouse system 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 from and to amount fields. You run the engine before running any other PeopleSoft EPM engines that require base currency amounts.

See Also

Setting Up and Running Currency Conversion for EPM Analytical Applications

Reviewing Installed Products

Before you can begin working with any PeopleSoft EPM application, you must specify installation options to indicate how you plan to use the system and which applications you will be using. Installation options are defined for your entire database—they are not specific to a business unit or setID.

This section discusses how to:

• Review installed PeopleSoft EPM products.

• Review installed PeopleSoft Enterprise Resource Planning (ERP) products.

• Set Web Services options.

Pages Used to Set Installation Options

Reviewing Installed PeopleSoft EPM Products

Access the EPM Products page.

EPM - Warehouses	The warehousing products that have been installed in your database are automatically selected.
EPM - EnterpriseOne and World Analytics	The PeopleSoft EnterpriseOne analytics and World Analytics products that have been installed in your database are automatically selected.
Enterprise Performance Management	The PeopleSoft EPM products that have been installed in your database are automatically selected.
Financial Services Performance Management	The financials services industry (FSI) products that have been installed in your database are automatically selected.
Other	Any other products that relate to your EPM implementation are automatically selected.
Default Information	Select the default country, which determines the address format for pages that use address fields. You define the address formats on the Country Table - Address Format page described later in this chapter.

Reviewing Installed PeopleSoft ERP Products

Access the ERP Products page.

Other PeopleSoft Products	Any other PeopleSoft ERP products that have been installed in your database are automatically selected.
Portal Products	Any PeopleSoft Portal products that have been installed in your database are automatically selected.

Setting Web Services Options

Access the Web Services page.

Allowed Concurrent Merges	Enter the number of concurrent merges allowed in your installation. The default is 3, which matches the number of record suites that are delivered with your system.
Process wait time (Seconds)	Enter the process wait time. The default is 60 seconds. Waiting improves performance of processes by eliminating repeated database requests.

Warning! Because each merge job in a jobstream reads in the number of concurrent updates, changing its value while merge processes are running can have unexpected results. Changes to the process wait time affect only subsequent runs of the engine.

See Also

Streamlining Processing with Jobstreams

Viewing Scorecard Results

Viewing Charts and Printing Results

Some PeopleSoft Enterprise Performance Management applications use charts. To view these charts, the AVS charting tool must be installed. In addition, complete the following procedure to set up required options:

1. Navigate to EPM Foundation, EPM Setup, Installation Analysis & Options, Installation Options, Web Services.

2. Select the Chart Server check box.

   This enables you to use the basic charting features.

3. To enable applets, select the Applets check box.

   Note that applets download code to the client workstation.

You can also print any of the pages that display results. To produce an optimal printout, set your internet browser to print background colors and images.

In Internet Explorer, follow these steps to set this option:

1. Select Tools, Internet Options.

2. Select the Advanced tab.

3. Scroll through the list of settings to view the Printing options.

4. Select the Print background colors and images check box, and click OK.

Specifying Your EPM Sources

This section provides an overview of the source system data and EPM and discusses how to define warehouse sources.

Understanding Source System Data and EPM Foundation

EPM Foundation enables you to extract, transform, and consolidate data from multiple source transaction systems into a series of target warehouse tables in the EPM database. This means that the EPM database can contain data from several Enterprise, Enterprise One, and third-party sources. Although the data is commingled in the EPM database, certain EPM processes require the ability to trace the data in target warehouse tables to its original source (original source transaction system). Other EPM processes use specific attributes associated with the source transaction system to process data. For example, the language swap utility uses the source system's base language for multiple language processing.

Because source system information is required, you must define the source in EPM and specify the attributes associated with that source using the Define Warehouse Sources page. Information specified on this page include source ID, base currency, and base language, and is used in several different EPM processes. Most notably, the source ID is used in the ETL process and helps to maintain source data history as well as data uniqueness. Currency and rate type are used in multiple currency processing. The source ID and default setID are used later to define warehouse business units.

See Also

Setting Up Multilanguage Processing

Setting Up and Running Currency Conversion for EPM Analytical Applications

Setting Up Warehouse Business Units

Page Used to Specify EPM Sources

Defining Warehouse Sources

Access the Define Warehouse Sources page.

Warehouse Source ID	Displays the unique source ID for the source transaction system from which you are extracting data. This code can be up to five characters long and is defined when you add a new source system. The source ID is primarily used for ETL processing.
Source DB Base Language Code (source database base language code)	Select the base language used by the specified source transaction system. This code is used for multiple language processing. See Setting Up Multilanguage Processing.
Source Type	Specify whether the source transaction system is an Enterprise, Enterprise One, or Other source.
Default Set ID	Enter a default setID for the tableset associated with the selected source system.

Defaults for WBU Creation (Defaults for Warehouse Business Unit Creation)

Setting Up Country and State Information

This section discusses how to:

• Review country descriptions.

• Select an address format by country.

• Validate addresses.

• Define countries for reporting.

• Specify state information.

Pages Used to Set up Country and State Information

Reviewing Country Descriptions

Access the Country Table - Country Description page.

The system displays the country code, description, and a short description for the country.

PeopleSoft delivers a fully populated country code table, which is updated as national boundaries and designations change.

Selecting an Address Format by Country

Access the Country Table - Address Format page.

Use this page to set up three aspects of the address: editing, displaying, and printing.

The address format that you specify on this page appears everywhere that the address subrecord is used in the system.

Validating Addresses

Access the Valid Address page.

To enable this page, select the Enable Address Search check box on the Address Format page, which enables the Used in Search column. The fields that you select to be used in a search appear on the Valid Address page as columns. Enter the valid address combinations that the user can search for and select.

Defining Countries for Reporting

Access the Country Statistics page.

Country	Select the country on which you want to report.
Use for Statistics	If this check box is selected, the country recognized by the International Standards Organization (ISO) is also recognized by the European statistical offices. If the check box is not selected, the country is recognized only by the ISO. In this case, European statistical offices assume that the country is a part of another country when producing statistical data such as the gross national product (GNP). For example, for the ISO, the principality of Monaco has its own country code, but for statistical purposes, Monaco is assumed to be part of France, and therefore has the same statistical country code as France.
2-Char Intrastat Country Cd (two-character intrastat country code)	The country identifier for the European statistical offices. This code often appears on intrastat layout forms.
2-Char ESL Country Cd (two-character ESL country code)	Used for countries that are members of the European Union. It usually appears as part of the VAT registration information on the European Sales List (ESL).
3-Dig Stat Country Cd (three-digit statistical country code)	Used as a country identifier for the European statistical offices. It usually appears on the intrastat report to identify source or destination countries to which or from which goods are shipped.
7-Char Country Descr (seven-character country description)	Used for the German international Electronic Funds Transfer (EFT) layout. It identifies countries into which or from which electronic funds are sent or received.
Sales/Use Tax Code	Informational only. This field can be set to None, Sales, or Use.

Note. PeopleSoft EPM only uses this page to establish the countries for statistical purposes. So most of the following information is for informational purposes only, because the reports mentioned are not available through the PeopleSoft EPM database. For more information on the reports mentioned in the following section, refer to the appropriate PeopleSoft Financials application documentation.

Specifying State Information

Access the State page.

PeopleSoft delivers a fully populated state code table. PeopleSoft updates the state table as changes occur. This table provides states, provinces, and equivalent geopolitical entities (for example, Dutch communities and French departments) for all supported countries. The codes are based on standard postal codes.

Setting Up Time Zones

EPM extract, transform, and load (ETL) jobs use the date time stamp in conjunction with source records to perform incremental loads. However, data can be extracted from multiple source transaction systems, each of which might reside in different database servers that use different time zones and different date and time stamps. This can lead to mismatched dates and times between the source and the EPM database. However, EPM target warehouse tables may include a source time zone field for records that have a date-time or time value depending upon the design and requirement.

When a target warehouse table contains a time zone field, prepackaged ETL jobs populate it with your source time zone values. Not all target warehouse tables contain a time zone field.

Note. Only one source time zone value can be populated in the target warehouse table.

Populating warehouse target tables with source time zone values is the first step in ensuring the synchronicity of source and EPM time zones. However, you are responsible for converting the source time zone value to the EPM database time zone.

Defining Accounting Calendars

This section provides an overview of accounting calendar setup, lists common elements, and discusses how to:

• Define a base calendar.

• Modify or add detail calendars.

• Define summary calendars.

• (Optional) Define business calendars.

• (Optional) Define daily calendars.

• (Optional) Define budget calendars.

• Define calendar frequencies.

• Define frequency details.

• Define timespans.

Understanding Accounting Calendar Setup

In PeopleSoft systems, you can establish an accounting period configuration based on the beginning and ending period dates that you normally use and combine these periods to create accounting calendars. These calendars define the time periods to which you post transactions or create reports for different ledger group and business unit combinations. You select the calendar that defines the periods for a business unit and ledger group combination.

You can maintain an unlimited number of accounting periods over any span of years. You can maintain traditional monthly periods, including an additional adjustment period, or you can define your own periods.

Note. In the PeopleSoft EPM product line, calendars are used mostly for reporting. However, for the system to properly handle data (for example, general ledger data) from your transaction database, you must be sure that the detail calendars match those in your transaction accounting system. You can move calendars from your PeopleSoft transaction database into your PeopleSoft EPM database using PeopleTools such as Data Mover.

The PeopleSoft system supports multiple calendars, so you can keep one calendar for actuals, another for budget and forecast activity, and still others for special reporting needs. Because you store calendars in tables, you can share them across business units, helping to provide consistency in period dates and easing the process of acquisition and consolidation.

PeopleSoft uses the following calendar definition options:

Common Elements Used in This Section

Pages Used to Define Accounting Calendars

Defining a Base Calendar

Access the Calendar Builder page.

Begin Date	Enter the beginning date for the calendar. The system uses this date and the end date to create the range of periods for the calendar.
End Date	Enter the end date for the calendar. The system uses this date with the begin date to create the range of periods for the calendar.
Start Fiscal Year	The system enters a default year for this field based on the year that you enter in the begin date field.
Calendar Method	Select one of the following options to determine the number of periods in the calendar: daily, weekly, bi-weekly, monthly, bi-monthly, quarterly, semi-annual, or yearly. For example, a daily calendar has 365 periods and a quarterly will have 4 periods. The system updates to display the number of periods in the Periods Per FY (periods per fiscal year) field.
Monthly Allocation Type	Use to select the appropriate period allocations for a monthly calendar. Select from the following: 12 period Calendar, 13 period Calendar, 445 Calendar (4 weeks, 4 weeks, 5 weeks), 454 Calendar (4 weeks, 5 weeks, 4 weeks), or 544 Calendar (5 weeks, 4 weeks, 4 weeks).
Generate	Click this option to have the system generate the calendar. The generated calendar periods display begin and end dates in the grid at the bottom of the page.
Period Name and Abbreviation	Use these fields to change the generated calendar period name and abbreviation if applicable.

Note. As you define calendars, keep in mind that in all instances in which a PeopleSoft EPM warehouse business unit is related to a general ledger business unit, the calendars for the business units should be the same. Warehouse business units are described elsewhere in this chapter.

After you have saved a calendar using the calendar builder, you can only modify the calendar description or long description on the Calendar Builder page. If you need to modify the saved calendar further, use the other calendar pages, (for example the Detail Calendar page).

By default, a calendar that you create with the Calendar Builder is a detail calendar.

Modifying or Adding Detail Calendars

Access the Detail Calendar page.

You create detail calendars using the Calendar Builder. Use this page to modify calendars after they have been created.

When you enter period dates, you can define monthly calendar periods or any fiscal period that matches your accounting calendar (such as weekly or bimonthly) as long as the beginning and ending dates of successive periods don't overlap. Every day of the year must be included in a period; you cannot leave gaps between period dates. Make sure that your detail calendar includes a period for the oldest transaction that you want to enter. After installing your PeopleSoft system, you might want to make this earliest date more restrictive.

You will need to return to this page to enter ensuing years manually. You can enter several years at a time or treat the task as part of your end-of-year system maintenance.

After you define your detail calendar, you can use it to manage open periods for the generation of journals. You can also use it to define the periods that store summarized results in a summary ledger.

Note. The MODEL calendar delivered with your system contains data from 1957 to 2025. You can use the MODEL calendar rather than entering your own data; if you do so, make a copy of MODEL first, and make changes to the copy.

Defining Summary Calendars

Access the Summary Budget Period Calendar page.

Consider the following when setting up summary calendars. A quarterly summary calendar, for example, might have four periods, each consisting of three periods from a monthly detail calendar. A summary calendar can also combine cumulative detail calendar accounting periods to create year-to-date balances. Summary calendars are especially useful for determining how your models will roll up for reporting purposes. As with detail calendars, you can include as many fiscal years as you need in one summary calendar.

Enter a description and periods per fiscal year to specify the number of periods in the accounting year for this calendar.

Supply the fiscal year, period, period name, and abbreviation.

Note. You can define as many years on a calendar as necessary. Be sure to include any years that you use to store historical information.

(Optional) Defining Business Calendars

Access the Business Day Calendar page.

Normal Business Days	Select the business days of the week to include.
Notes	Enter any notes to further describe this calendar.

In the grid at the bottom of the page enter a row for each holiday on which you know businesses won't operate.

In multinational corporations, you accommodate the various locations and different holidays observed by defining as many business calendars as you need for each setID.

Note. Business calendars determine the number of workdays in each month, for reporting purposes only.

Note. If you use PeopleSoft Asset Liability Management, Funds Transfer Pricing, or Risk-Weighted Capital, you must create a business day calendar to define your holidays.

(Optional) Defining Daily Calendars

Access the Daily Calendar page.

Create	Click to access the Create Detail Periods secondary page, on which you can enter the fiscal year and start date for creating daily periods.
Update	Click to access the Create Detail Periods secondary page, on which you can enter a new fiscal year.

Remember to set up a calendar for each fiscal year. To display the detail periods for existing calendars, click the Update button.

Note. For leap years, you must change the periods per fiscal year value from 365 to 366 to create the last period for the leap year (for example, December 31, 2004).

(Optional) Defining Budget Calendars

Access the Budget Calendar page.

For budget calendars, you might want to enter a descriptive calendar ID such as AN for an annual calendar budget.

Enter the budget periods, begin and end dates, and period names.

Defining Calendar Frequencies

Access the Frequency Definition page.

Define frequencies by adding a row with a description or by updating an existing description.

Note. The frequencies you define on this page will comprise the list of valid values in the Frequency Details page.

Defining Frequency Details

Access the Frequency Details page.

Calendar ID

Select a calendar. The calendar ID that you select represents the calendar that you want to associate with the frequency. You can have more than one frequency defined for a single calendar. The system updates to display calendar detail. You can also specify all frequencies that are associated with any other frequency definition for this frequency group. You can define frequency relationships across multiple calendars.

Process

Select for any of the accounting periods that you want to process.

Defining Timespans

Access the TimeSpan page.

Start Year and Start Period	Enter the appropriate value. The value that you enter depends on the type that you select.
End Year and End Period	Enter the appropriate value. The value that you enter depends on the type that you select.
Type	Select from the following: Absolute Period or Absolute Year: You can enter any year or period that has been defined in the timespans calendar. Relative to Current Period or Relative to Current Year: Enter 0 as the period or year to select the current year or period, -1 to indicate the previous year or period, 1 to indicate the next, and so forth.
Use Scenario Calendar	Select this check box to use the specified scenario calendar with this timespan. This enables you to have a scenario-based timespan.
Include Balance Forward	Select this check box if you use nVision for the consolidation ledger or any ledger with balance forward accounts. If you select this check box, nVision will compute ledger balance.
Calendar ID	Select the calendar that you want to use with this timespan.

Note. Balance forward accounts store balance forward amounts. For example, in your regular accounting system you might want to specify asset, liability, and equity accounts as balance forward accounts, but not revenue or expense accounts. The account balance forward function rolls forward the accounts on any date specified for flexible year-end processing.

See Also

PeopleSoft Enterprise Global Consolidations 8.9 PeopleBook

Setting Up the Gregorian Calendar for the Performance Management Warehouse

The Calendar dimension represents calendars that fall into two broad functional categories. The Gregorian calendar (the calendar that is commonly used) has one row for each day. The business calendar represents the functionality the PeopleSoft provides to define various types of business calendars, such as detail calendars, summary calendars, budget calendars, and so on.

Gregorian calendar setup is a onetime setup as part of the MDW setup. You can generate the Gregorian calendar for a range of years. For each day in the year range, the Gregorian calendar has one row. (You do not define business calendars in the MDW; their definitions are imported from source systems and the OWE).

To set up the Gregorian calendar, use the Day Dimension (D_DAY) component and the Time Dimension (D_TIME) component.

This section discusses how to set up the Gregorian Calendar for the Performance Management Warehouse.

Pages Used to Set Up the Gregorian Calendar

Populating the Day Dimension

Access the Day Dimension page.

Start Date	Enter the beginning date for this calendar.
End Date	Enter the ending date for this calendar.
Jobstream ID	Enter D_DAY.
Weekend Flag	Check the days that represent weekend days.
Retry Enabled	This field will be available for future use.

Save the page and click Run.

Click the Process Monitor link to check the status of application engine program. After a period of time, it should display the status as Success.

Populating the Time Dimension

Access the Time Dimension page.

Time Format	Select either 12 Hour Format or 24 Hour Format.
Retry Enabled	This field will be available for future use.

Save the page and click Run.

Click the Process Monitor link to check the status of application engine program. After a period of time, it should display the status as Success.

Defining Operator Defaults

Operator defaults enable you to assign a default business unit and setID for each user per country. You specify operator defaults on the Operator Defaults page.

Page Used to Specify Operator Defaults

Specifying Default User Preferences

Access the Operator Defaults page.

Business Unit and SetID	The values that you select become the user's default values in the business unit and setID search fields.
Localization Country	Enter the default country for this user ID.

Note. You can control the business unit, setID, and address format default values by using the Operator Defaults page.

Defining Units of Measure

Units of measure (UOM) determine how resources are quantified. Each resource must be associated with a standard unit of measure. Standardization helps you to control the units that appear in reports and enables you to use the PeopleSoft automatic conversion features.

This section discusses how to:

• Import UOM values from a source.

• Display and modify UOMs.

Page Used to Define UOMs

Importing UOM Values from Your Source

EPM enables you to extract and consolidate source data from various source transaction systems. Certain source systems might contain UOM values different from those offered in EPM. This causes mismatched UOM values between the source and the EPM database. However, EPM target warehouse tables include source UOM definitions and conversion rate fields for all records that store UOM data. Prepackaged ETL jobs populate these fields with your source UOM definitions and conversion rate values.

PeopleSoft-delivered ETL jobs populate the following target warehouse tables with UOM values:

• UNITS_TBL

• UNITS_CVT_TBL

• INV_ITEM (for Supply Chain Management only)

• UOM_TYPE_INV (for Supply Chain Management only)

Populating warehouse target tables with source UOM values is the first step in ensuring the synchronicity of source and EPM UOM values. However, you are responsible for converting the source UOM value to the EPM database UOM.

Displaying and Modifying UOMs

Access the Unit of Measure page.

Convert To, Conversion Rate, and Inverse Conversion Rate

Specify the conversion rules of a particular UOM. For example, by specifying a conversion from cubic feet to cubic yards and an appropriate conversion rate, when you enter a resource amount in cubic feet, the system automatically converts the amount to cubic yards. Automatic conversion is a key feature of PeopleSoft statistical accounting. It enables you to enter resource amounts in whatever unit is readily available or convenient at the time, and converts the units to the required standard. The system also automatically calculates the inverse conversion rate.

Setting Up Multilanguage Processing

This section provides an overview of multilanguage processing and setups and discusses how to:

• Map Enterprise One language codes to Enterprise language codes.

• Run the language swap utility.

Understanding Multilanguage Processing

Many organizations conduct business globally and deploy their transaction (ERP) systems in various locations throughout the world. As a result, the ERP systems record data in various languages. PeopleSoft supports multilanguage processing and enables you to:

• Import descriptions for any language into EPM target warehouse tables.

• Exchange descriptions in source tables with the related-language tables, when source defined language is different than the EPM defined language.

• Report in different languages.

PeopleSoft delivers related language tables and ETL jobs to enable multilanguage processing. Related language tables are defined for every DIM and D00 table that contain translatable values. For example, the table CUSTOMER_D00 has a corresponding related language table CUSTOMER_LNG. Related language tables have key structures identical to the related DIM and D00 table plus one additional key field called language code (LANGUAGE_CD). The language code field holds the source language value. Prepackaged ETL jobs populate this field with your source language value.

Language Swap Utility

Because EPM can extract and consolidate data from various source transaction systems with various languages, it is possible that the language defined in the source is different from the language defined in the EPM database. If this mismatch of languages occur, your descriptions cannot be translated to your desired language.

The language swap utility automatically detects the mismatched languages and sets the correct base language for incoming data. The utility compares the base language of the source database (as it is stored in the SRC_SYSTEM_TBL) and the base language of the EPM database. If they are different, the utility swaps the descriptions that are found in the base table and the related-language tables whenever possible. Once the data are in OWS and the base language swap utility has been performed, the reference data and their related language data in OWS are conformed to the PeopleSoft infrastructure for related language. This ensures proper synchronization and enables you to process and report in multiple languages. Note, however, that this process requires that descriptions be available in the source record. This process cannot be performed if the related language record doesn't have any description fields, or any other fields that are translatable, from the base table.

The following graphic depicts the language swap process.

Language swap process

The language swap utility is embedded in prepackaged ETL jobs and should be run only when your source database language is different from the language defined for the EPM database.

Outrigger Tables for the Multidimensional Warehouse

Outrigger tables are records that represent country-specific attributes in a dimensional data model. The outrigger record is a separate table in the MDW that is an extension of the base dimension table. It has all of the keys of the base dimension table, plus a language code (LANGUAGE_CD). The outrigger table contains attributes for all supported country and dimension values in the base dimension table. That is, in the outrigger table there is an entry for every entry in the base table in every language in the related language table. For example, if there are ten entries in the base table and there are three supported languages, there will be 30 entries in the corresponding outrigger table.

If, however, there is no corresponding description (that is, translation) for a particular entry for one of the languages in the related language, the description defaults to the value in the base table.

This table shows an example of a Sales fact table:

This table shows an example of the related Product dimension table:

Typically, if a dimension table is used in conjunction with an outrigger table, the dimension table does not have any attributes that are country-specific. This is to prevent duplicate attributes in the dimension table and the outrigger table.

This table shows an example of the related Product outrigger table, assuming the base language is English (ENG) and the supported languages are English (ENG), German (DUT), and Italian (ITA):

When you constrain language code to a single value, your reporting tool uses the attributes from the outrigger table (Product Description) and the Product dimension table (SKU and Description) to qualify the metrics (Amount and Quantity) and produce the description in the selected language.

Note. In this example, if the related language table did not contain a German description for Bread, the description for Bread in German in this outrigger table would contain Bread, rather than Brot.

You use ETL to populate outrigger tables at the time that you populate the MDW layer.

See Loading Data into the Multidimensional Warehouse.

Understanding Multilanguage Setup

You must enable multilanguage processing before you can view your data in a different language or run multilanguage reports. Setting up multilanguage processing requires three simple steps:

• Define the base language of your source systems: Use the Define Warehouse Source page to perform this task.

  See Specifying Your EPM Sources.

• Map Enterprise One language codes to Enterprise language codes.

• Run the language swap utility.

Language Code Mapping

Enterprise One language codes are user defined so they do not conform to standard EPM language codes. For example, the language code for English in Enterprise One can be ES, while the language code for English in EPM is ENG. Mismatched language codes can create unexpected results with your EPM data. Therefore, you must map the Enterprise One language code to the standard EPM language code. The mapping information is used during the ETL process to reconcile the conflicting language codes. Use the E1 Language Code Mapping page to map Enterprise One language codes to Enterprise language codes.

Page Used to Setup Multi-Language Processing

Mapping Language Codes

Access the E1 Language Code Mapping page.

Source System Identification	Select the Enterprise One source system that contains the language code you are mapping.
E1 Language Code	Enter the Enterprise One language code that you are mapping.
Language Code	Select the language that your selected code represents.

Running the Language Swap Utility

The language swap process is a part of the PeopleSoft ETL sequencer job SEQ_J_Run_LangSwap. Simply run the job to initiate the language swap process. Please note, however, that this process should not be run until you run all staging jobs that populate base tables and language tables.

Setting Up Currency Tables

Currency code pages define each currency that you use. To meet your multicurrency requirements, PeopleSoft supports the euro and delivers the Currency Code table with many common ISO standard currencies. The table also supports the ISO standard of zero, two, and three decimal positions.

This section discusses how to:

• Maintain currency codes.

• Update the status of a euro currency code.

Pages Used to Maintain Currency Tables

Maintaining Currency Codes

Access the Currency Code page.

Currency Symbol	PeopleSoft delivers many currencies with a currency symbol such as $ for Australian dollar (AUD) or ? for British pound (GBP). You can enter new symbols for delivered currencies or for currencies that you might add.
Country	Displays the code for the country from which the currency originates.
Decimal Positions	Enter the number of decimal positions that should appear in the notation for the currency. For example, use two decimal positions for Australian dollars (5.00 AUD), but no decimal positions for Japanese yen (500 JPY).
Scale Positions	Enter the scale positions that you want to round for this currency. Scale positions control how many numbers appear to the left of the decimal when displayed. The data is stored with full precision in the database. For example, if you want all dollar amounts in the millions displayed as the number of millions without the zeros, enter 6 as your scale position. In this case, 24,000,000 is displayed as 24, but is stored in the database as 24,000,000.

Note. The data on this page is stored in the Currency Code table. The values on this table are effective-dated. The software is shipped with the Currency Code table in compliance with ISO standards for decimal positions. You can increase the number of decimals to a maximum of three.

Note. PeopleSoft updates the Currency Code table and the fully populated country, state, and province code tables as national boundaries and designations change.

Updating the Status of a Euro Currency Code

Access the Currency Code (Euro) page.

Status

Displays whether a currency is an active participant in the euro.

Note. Do not attempt to modify the currency quotation methods for currencies that are linked to the euro.

Setting Up Market Rates

The PeopleSoft approach to market rates and currency conversion is driven by the need to accommodate business practices related to the European Common Currency (euro). In addition to currency exchange rates, PeopleSoft supports the many different types of global market rates, such as interest rates, stock exchange indexes, and economic indicators.

This section discusses how to:

• Define market rate indexes.

• Define market rate types.

• Define market rate tolerances.

Pages Used to Define Market Rates

Defining Market Rate Indexes

Access the Market Rate Index page.

Rate Category	Select a Rate Category from the list: Options include: Commodity Price, Economic Indicator, Exchange Rate, Futures Price, Interest Rate, Other, Stock Exchange, Index, or Stock Price.
Default Exchange Rate Index	If you are entering exchange rate indexes, select this check box to indicate which index should be used to retrieve currency exchange rates. You can specify only one index code as the default.

Defining Market Rate Types

Access the Market Rate Type page.

Enter a description and short description for each market rate type that you use.

Defining Market Rate Tolerances

Access the Market Rate Definition page.

The information that appears on this page depends on the type of index that you select. For example, if you select an index with interest rates, interest rates appear on this page.

Market rate definitions specify the valid term, currency, and other appropriate field combinations for market rates. For example, if you have a market rate definition for an exchange rate with a term of 30, a from currency of EUR, and a to currency of USD, you can enter a rate using this combination in the market rate table. If you do not have a market rate definition, the system creates one for you using the default values.

Defining Currency Quotations

This section provides an overview of currency quotations and discusses how to maintain currency quotation methods.

Understanding Currency Quotations

PeopleSoft supports direct and indirect rate quotation, quote units, and triangulation. These are flexible and accurate tools that enable you to convert and manage multicurrency operations.

The currency quotation method controls how a stored rate is displayed and how an entered rate is interpreted and stored in the database. You set up and maintain a currency quotation method for each from currency and to currency pair.

You do not typically maintain rates online for currency pairs that triangulate. Instead, the Cross rate/Triangulation Generation SQR determines the cross rate by using the rates between the from currency and the reference currency, and between the reference currency and the to currency.

Currency quotation methods must be set up correctly to yield the desired triangulation results.

Note. Define currency quotation options before you enter the rates and before you calculate the rates.

Page Used to Define and Maintain Currency Quotations

Maintaining Currency Quotation Methods

Access the Currency Quotation Method page.

Rate Quotation Basis

Note. Currency pairs that triangulate must be classified as either direct or indirect to use in displaying the calculated cross rate. Two fields store the rate conversion factor: RATE_DIV and RATE_MULT. The currency conversion formula is always: (From currency ÷ RATE_DIV) ? (RATE_MULT) = To currency

Triangulation Options

Select the Triangulate check box to have the system convert two currencies through a third currency (the reference currency). Triangulation is used in hyperinflationary environments in which all conversions to the local currency are done through a more stable currency such as USD.

Note. Triangulation was initially used for European countries participating in the euro. However, since 1999 all countries participating in the euro are quoted directly against the foreign currency.

Any countries newly participating in the euro might be initially subject to triangulation, however. The triangulation example below and any other examples in this chapter that show triangulation, use a fictional country, with a currency code of NEW, that has just joined the euro. This country is subject to triangulation.

The following are examples of indirect quotation, direct quotation with quote units, and triangulation:

USD 100 to GBP (indirect) = (USD 100 x 1.6) x 1 = GBP 62.50.

CHF 1000 to German marks (DEM) (direct with units) = (CHF 1000 / 100) x 119.335 = DEM 1193.35.

USD 100 to NEW (triangulate) = (USD 100 / 1.25) x 6.8 = NEW 544.

For example, to convert from USD to NEW with triangulation, you perform two conversions:

• Convert the USD amount to the reference currency using the appropriate triangulated rate.

  The triangulated rate uses the USD to EUR component of the USD to NEW triangulated rate that is stored in RATE_DIV.

• Convert the reference currency to NEW using the fixed exchange rate.

  The exchange rate uses the EUR to NEW component of the USD to NEW triangulated rate that is stored in RATE_MULT.

Typically, you do not maintain triangulation rates directly. Instead, you process these and all rates through the Cross/Reciprocal Rate Calculator.

Select a reference currency through which the from currency will be converted.

You must consider three exchange rates for triangulated currency pairs:

• The rate between the from currency code and reference currencies.

• The rate between the reference and the to currency code currencies.

• The cross rate between the from currency code and to currency code currencies.

Primary Visual Rate

Select one of the three conversion rates as the primary rate that appears on primary pages and reports.

Cross Rate

Select the Allow Override check box to enable users to override the cross rate for a triangulated currency pair. If this option is cleared, you can change the components of only the triangulated rate.

Recalculate

If you select the Allow Override check box, you must maintain triangulation accuracy by specifying which currency pair the system should use to recalculate if the cross rate is overridden.

Automatic Reciprocation of Quote Methods

The Currency Quotation Method page automatically provides reciprocal methods. For example, if you define the conversion of USD to NEW as indirect, this record is automatically created to indicate a quote method of direct. If you change the quote method on the NEW to USD record, the USD to NEW record is updated automatically.

Note. This example uses a hypothetical currency NEW that has just begun participating in the euro and is still subject to triangulation for an initial period.

Using the conversion of USD to NEW as an example, this table shows each possible field value and its corresponding reciprocal value.

Establishing Market Rates

This section discusses how to:

• Define market rates.

• Establish rate definitions.

• Maintain exchange rates.

• Load market rates.

Pages Used to Establish Market Rates

Defining Market Rates

Access the Market Rate page.

Rate	The Rate field displays the visual rate or, in the case of triangulated exchange rates, the primary visual rate. The visual rate is typically the cross rate, but it can also be one of the other component rates of the triangle.

You can edit the rate for non triangulated rates and for triangulated rates if a quotation method has been defined for the currency pair and the Cross rate Allow Overridecheck box is selected on the Currency Quotation Method page. If an override is not allowed, you can update the exchange rate values to and from the reference currency on the Exchange Rate Detail page.

Changing a Triangulated Cross Rate

If you change a triangulated cross rate, the system recalculates one of the component rates. This can result in the cross rate being recalculated in a manner that is slightly different from the one that you entered. For example, you start with a triangulated rate of RM=6.80000000 and RD=1.25000000 for a cross rate of 5.44000000. If you change the cross rate to 5.43550000:

• The system first recalculates RD to 1.25103486.

• The system then recalculates the cross rate to 5.43550001 based on the first recalculation.

In rate maintenance, you must accept the recalculation. However, in a situation such as journal entry, a warning message enables you to override triangulation and to use the exact rate that you entered, which results in the rate being stored as RM equal to 5.43550000 and RD equal to 1.

You can edit the Rate field except when all of these conditions are true:

• The rate is triangulated.

• The primary visual rate is the cross rate.

• The Allow Override check box on the Currency Quotation Method page is cleared for the exchange rate's quotation method.

Note. Typically, you do not maintain triangulated exchange rates online. Instead, maintain the rates of the from currency to the reference currency and the reference currency to the to currency, and then run the Cross rate Reciprocal SQR (EO9030.SQR) to define the triangulated exchange rates.

Reciprocal Currency Pairs

If a quotation method has been defined for the currency pair and if the Auto Reciprocate check box is selected, creating or maintaining a rate for a currency pair automatically creates or updates the rate of the reciprocal currency pair. For example, if you change the USD to GBP rate, the GBP to USD rate automatically is automatically updated. You can only automatically reciprocate currency pairs for which quotation methods have been defined.

If a rate definition does not already exist for the currency pair, one will be automatically created with the default values of 2.5 percent maximum variance and warning message processing.

Establishing Rate Definitions

Access the Market Rate - Rate Definition page.

Maximum Variance	You can modify the maximum variance—that is, the percentage of variance allowed when you maintain the market rate. If the change exceeds the tolerance, an error results. The default value is 2.50 (2.5 percent).
Error Type	You can modify the type of error that results when the tolerance defined in the Maximum Variance field is exceeded during data entry. Error type values are: None: No error processing occurs. The new rate is used even though it exceeds the limit. Stop : Processing halts. The system prevents you from saving the new rate. Warning: A warning appears. You can ignore it and save the new rate.

Note. The results of changing the rate definition do not take effect until you save the Market Rates page.

Click OK to return to the Market Rates page.

Maintaining Exchange Rates

Access the Market Rate - Exchange Rate Detail page.

The read-only fields include:

Loading Market Rates

Market rates can be loaded to the RT_RATE_TBL from any external source using the DataStage ETL tool.

Note. Use the Market Rates page to verify that the market rates were loaded correctly.

Calculating Currency Rates

This section provide an overview of currency calculations and discusses how to:

• Calculate cross rates and reciprocal rates.

• Run the Currency Exchange Calculator tool.

Understanding Currency Calculations

PeopleSoft calculates currency rates for cross rates, triangulated rates, and reciprocal rates.

PeopleSoft applications utilize two tools for currency calculations:

• The Currency Exchange Calculator tool quickly performs ad hoc currency conversion using the exchange rates that are stored on the market rates table.

• The Cross/Reciprocal Rate Calculator calculates exchange rates and updates the market rates table.

  It performs three functions by generating the rates shown in this table:

Pages Used to Calculate Currency Rates

Calculating Cross Rates and Reciprocal Rates

Access the Cross/Reciprocal Rate Calculator page.

Language Code	Select the language for translation.
Market Rate Index	Select a market rate index.
Term	The system displays this value by default from the value entered on the Market Rate Definition page.
From Common Currency	Select a currency code from which to calculate a reciprocal rate.
Exchange Rate Type	Select the type of exchange rate to use for this calculation.
As of Date	Determines the effective date of newly created exchange rates (the output of the process) and rates that are used as the basis for calculations (the input to the process). The report uses the most current currency quotation method for the currency pair as input for the process. If the as of date is the current effective rate as of the specified date, it can affect triangulation.
Generate Report	Select to specify that the system generate a report that displays exchange rates and reciprocal and cross rate calculations.
Override Existing Rates	Select to direct the calculated rate to override rates for the exchange rate type, regardless of the as of date.

Generating Reciprocal Rates

You can select the Generate Reciprocal Rate check box by itself or in combination with the Rate Triangulate and Generate Cross Rate check boxes. When this option is selected, the system automatically calculates reciprocal rates for currency pairs for which the autoreciprocate option on the currency method is disabled.

The system does not directly manipulate the exchange rates. The system uses numerator and denominator values such that:

(From currency / RATE_DIV) x RATE_MULT = To currency

Generating Cross Rates

When you select the Generate Cross Rates check box, the system automatically generate cross rates. For example, to generate cross-currency rates for USD, (CAD), and (MXP), you enter USD to CAD = 1.473 and USD to MXP = 9.8793. The system automatically generates CAD to MXP = 9.8793 / 1.473 = 6.7069246.

If you generate cross rates, you must select a from currency and a to currency. You can enter a wild card of % in either field or both fields to indicatefrom all orto all currencies.

Generating Triangulation Rates

When you select the Rate Triangulate check box, the system converts two currencies through a third currency. If you select rate triangulation, you must select a from currency and a to currency. You can enter a wild card of % in either field or both fields to indicate from all or to all currencies.

Running the Currency Exchange Calculator Tool

Access the Currency Exchange Calculator page.

This tool enables you to enter a rate or an amount in a currency other than the base currency, or to compute an exchange using an alternative rate type.

Note. Do not decrease the number of decimals after you have created transactions for that currency; the system will not properly round the previous rounded amount fields with the new precision.

Configuring Currency Precision

This section provides an overview of currency precision and discusses how to:

• Activate currency precision.

• Maintain currency precision by currency.

• Report with currency precision.

Understanding Currency Precision

According to the ISO standard, currency precision can range from zero decimals to three decimals. For example, USD amounts have two digits to the right of the decimal, and JPY have none. To support this dynamic currency precision, the system delivers all of its currency-sensitive amount fields with a standard length of 23.3, or 23 digits to the left of the decimal and three digits to the right. A control currency on the same record exists to control the display and processing of such amount fields.

PeopleSoft applications round all currency-sensitive amount fields to the currency precision of the controlled currency during all online or background processes. For example, in a database that contains amount fields with a length of 23.3, JPY are rounded to 123.000 and USD are rounded to 123.230. The system does not place a nonzero after the decimal for a JPY amount or after the second digit to the right of the decimal for a USD amount.

Although amount fields are stored in the database with decimal placeholders, the system displays amount fields with the precision that is appropriate for the currency. For example, it displays JPY as 123 and USD as 123.23. When you enter an amount, you cannot enter more than the defined precision. If you attempt to do so, the system treats the entry as an online error.

PeopleCode programs and background processes round all currency-sensitive amount fields to the currency precision of the controlled currency.

See Also

Configuring Currency Precision

Activating Currency Precision

Currency precision is a PeopleSoft PeopleTools option. When it is selected using the PeopleTools Options page, all features of currency precision are activated. When the option is cleared, all amount fields behave as if no controlled currency exists. The system displays amount fields as defined in the PeopleSoft Application Designer and rounds them to the number of decimals defined in the Application Designer.

Note. If you clear the multicurrency check box, the system only supports the default amount field size of 15.3—it does not support the larger amount field size of 23.3. After you clear this check box, selecting it again does not automatically round existing transaction amounts.

Maintaining Currency Precision by Currency

Use the Currency Code page to access the currency code table, in which you define the decimal position by currency. The values in this table are effective dated. The software is shipped with the currency code table in compliance with ISO standards for decimal positions. You can increase the number of decimals to a maximum of three.

Warning! Do not decrease the number of decimals after transactions are entered in that currency; the system does not properly round the previously rounded amount fields with the new precision.

See Also

Maintaining Currency Codes

Reporting with Currency Precision

Most PeopleSoft SQR reports display currency-controlled amounts with the number of decimal places that are defined by the associated currency. For example, a JPY amount appears as 123 on a report, and a United USD amount appears as 123.23.

Amounts on Crystal and PS/nVision (Microsoft Excel) reports appear as two-decimal-place numbers. If you want to show three decimal places on these reports, you must configure the reports to do so.

Third-party reporting tools used by PeopleSoft do not fully support numeric fields greater than 15 digits. Microsoft Excel uses an eight-byte float for numeric fields, which causes values to be truncated after the fifteenth digit.

Crystal displays up to 15 digits correctly. When a value exceeds 15 digits, Crystal inserts invalid numbers into the decimal positions. This is an issue for only very large currency amounts. For any of these reporting tools, the accuracy of the results is:

• Hundreds of trillions of yen (precision = 0).

• Trillions of dollars (precision = 2).

• Hundreds of billions of dinar (precision = 3).

For example, if you populate a 23.3 numeric database amount field with the number 2, the following table illustrates the number that is displayed in each type of report.

Setting Up and Running Currency Conversion for EPM Analytical Applications

This section provides an overview of currency conversion, lists the delivered metadata, and discusses how to:

• Describe currency conversion rules.

• Create currency conversion rule sets.

• Associate a conversion rule set with a job.

• Run currency conversion.

• Review multicurrency conversion messages.

Understanding Currency Conversion

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.

Although data may be brought into PeopleSoft Performance Management Warehouse in multiple currencies, the amounts must be converted to a single currency for each business unit 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).

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.

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.

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 currency conversion.

See Also

Setting Up and Working with EPM Foundation Metadata

Setting Up Job Metadata

Pages Used to Set Up and Run 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 Currency Conversion

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

Setting Up and Running Currency Conversion for the Performance Management Warehouse

To set up and run the currency conversion process for the Performance Management Warehouse, use the Currency Conversion Schema Definition (CCU_SCHEMA_DEFN) component and the Currency Conversion Definition (CCU_CONV_DEFN) component.

This section provides overviews of the Performance Management Warehouse currency conversion process and currency conversion rules and discusses how to:

• Set up currency conversion.

• Set up the schema definition.

• Set up currency conversion rules.

• Set up the conversion schema rule.

• Run currency conversion process.

Understanding the Currency Conversion Process for the Performance Management Warehouse

Companies spanning national boundaries often experience problems handling multiple currencies, as well as problems providing a unified view of their enterprise data. This can occur because transactional data can be kept in any currency in which the company does business.

To overcome this disparity, information in MDW fact tables is kept in more than one currency: the source currency and up to two additional currencies. To process data in more than one currency, you must potentially convert transactions from one currency to another currency. You do this using the PeopleSoft MDW Currency Conversion utility for the Performance Management Warehouse, an ETL process that you run after you populate the MDW.

Note. The MDW post-ETL Currency Conversion process discussed in this chapter populates MDW tables only. Do not confuse this process with the currency conversion application engine process that populates the OWE and is used with the analytical applications.

Enterprise One currency codes are user-defined and may not match EPM currency codes, which are system-defined.

Currency Conversion

The ETL process that populates the MDW fact tables does not populate the reporting1 and reporting2 amount fields, nor their corresponding reporting currency code fields. After you run the ETL process to populate MDW fact tables, you must run the ETL Currency Conversion process if you need to populate these fields.

You can perform this process using both a direct exchange rate and a triangulated exchange rate. (A triangulated exchange rate conversion takes place when no direct exchange rate between a from currency and a to currency exist, but the exchange rates exist between the from currency and a reference currency, and from the reference currency the to currency. Using the triangulation method, the currency conversion process indirectly establishes the exchange rates between a from currency and a to currency using the intermediary reference currency). You set up triangulation parameters with other EPM setup functions.

If you provide an optional exchange rate date parameter, the currency conversion process searches for an exchange rate for a given exchange rate date. If you do not provide an exchange rate date parameter, the conversion utility uses the date of the transaction to determine the exchange rate.

Note. The MDW currency conversion process does not perform balancing; that is, when there are parent and child tables and rounding occurs, the process does not ensure that the sum of the child tables equals the value of the parent table.

If you map multiple source business units into one warehouse business unit (WBU), the default currency of the source business units must be the same as the default currency of the warehouse business unit.

Fact Tables and Currency Codes

Every source amount that is stored in an MDW fact table must have a corresponding source currency code field in that fact table. Additionally, because each fact table can carry the source currency code and up to two additional currencies, each fact table can have up to two additional currency codes. Therefore, each source amount in a fact table has a corresponding reporting1 amount and a reporting2 amount. Because all currency amount columns must have a corresponding currency code, each reporting1 and reporting2 amount have a respective reporting currency code1 and reporting currency code2. Following is an example of currency and currency code fields in a fact table showing the transaction currency (AMOUNT column), its currency code (AMT_CD) and reporting1 and 2 amount columns and their respective currency code columns:

Base amount and base currency code fields can also exist in the MDW fact table. However, they exist only if the source table has the corresponding base amount and base currency code fields, and only if a currency conversion process was run on that database. (The currency conversion process run on the source database is an application engine process and is not the same ETL currency conversion post-process described in this section). The base amount and transaction amount are considered source amounts.

The reporting amounts (RPT_AMT1 and RPT_AMT2 in the fact table example) are populated as a result of the ETL currency conversion process that you run after populating the MDW. Their values do not exist in the source system. The report amounts can represent amounts in any currency you choose.

Assuming the source currency amount is <ABC>_AMT, where “<ABC>” represents the name of the field, the currency field naming convention for MDW fact tables is:

Understanding Currency Conversion Rules

The parameters for MDW currency conversion fall into three categories, or rules: schema rules, currency rules, and chunking rules. Together, these three rules are referred to as currency conversion rules.

Schema Rules

Schema rules specify on what table the currency conversion is performed, the source amount and currency code column, and target amount and currency code column that is populated by the conversion result. Schema rules also include the table name where the source and target columns are found.

You set up the schema rules based on the schema definition, which is system data and is delivered as part of the PeopleSoft EPM product. The predefined schema definition associates source amounts and currency code fields to their target amount and currency code fields. Schema rules contain the list of all target columns for currency conversion, along with their associated information, such as the record name, Source Amount column, the Source Currency Code column, and the To Currency Code column for a particular fact table.

It is important to understand the difference between the schema definition and the schema rules. The schema definition only records the relationship of columns in delivered tables. A schema rule is customer-specific because it depends on what rate and date to use for a currency conversion. For example, the schema definition only indicates the currency code column for a particular amount column in a stated table.

See Setting Up the Schema Definition.

Conversion Rules

Conversion rules are the rules that specify the rate type, the target currency code, and the data that determines the effective rate to use for the currency conversion process.

Conversion rules are user-defined data and are not delivered as part of the EPM product. Because exchange rate rules are specific to user requirements, and therefore they are treated as user data, PeopleSoft provides only sample data with your EPM product.

Exchange rate rules consist of:

• Rate Type.

• To currency code.

• Conversion date.

  You must choose either:

  • To give the specific exchange date that the currency conversion process will use to identify the exchange rate.

  • To have the currency conversion process use the processing date.

  • To have the currency conversion process use the exchange date column as specified in the schema rule.

Chunking Rules

Chunking rules are parameters that the currency conversion process uses to identify the subset of data in MDW tables that are affected by the conversion process. Chunking rules are considered part of the currency conversion rules. They are specific to user requirements and are treated as user data. Therefore, PeopleSoft provides only sample data with your EPM product.

Chunking rules consist of performance (PF) business unit, start date, and end date. These parameters are optional. If you do not provide business unit and chunking date parameters, the process performs conversion on the entire table.

Setting Up Currency Conversion

You run the currency conversion process from a run control page, which takes as its input a Currency Conversion Rule ID, which is a composite of the conversion rules whose parameters you have set up before you run the currency conversion process. The Currency Conversion Rule ID provides the necessary information to perform the currency conversion, such as the rule to obtain the appropriate exchange rate, the rule to obtain the subset of data on which the currency conversion is performed, and the source and target columns for currency conversion.

To set up currency conversion, use the Schema Definition (CCU_SCHEMA_DEFN) component and the Currency Conversion (CCU_CONV_DEFN) component.

Before you run the ETL currency conversion process, you must define the required parameters. This section discusses how to:

1. Set up the schema definition and columns.

2. Define schema source columns.

3. Define schema target columns.

4. Define rules for currency conversion.

Pages Used to Set Up the Schema Definition and Currency Conversion Rules

Setting Up the Schema Definition

Access the Schema Definition page.

Business Unit Column	Enter the name of the PF (performance) business unit column.
MDW Fact Exchange Dt Column (MDW Fact Exchange Date Column)	Enter the date column used to determine the exchange date or conversion date.
Date/Period Dimension Record	Enter the level (year, month, day, and so on) for the Fact Exchange Date column.
Address Book Column	Enter the column that indicates the Address Book value. This value is required only if the fact table has an Address Book entry.

Setting Up MDW Currency Conversion Rules

Access the MDW Currency Conversion Rule page.

Currency Conversion Rule

The name of the currency conversion rule.

Conversion Rule Definition

Chunking Rule Definition

Setting up the MDW Conversion Schema Rule

Access the MDW Conversion Schema Rule page.

Record (Table) Name	Select the record on which the conversion will be performed. The record name must exist in the schema definition.
To Amount Column	Select the column for the conversion result. The options are obtained from the schema definition.
From Amount Column	The column to be converted. This field is automatically populated from the schema definition when you select the To Amount Column.

Running the MDW Currency Conversion Process

The MDW Currency Conversion process is an ETL utility that you launch through the ETL run control page. On this page, you must enter:

• The map name.

• The Currency Conversion Rule ID.

The Currency Conversion Rule ID exists on the MDW Conversion Schema Rule and the MDW Conversion Schema Rule pages. The Currency Conversion Rule ID provides the MDW Currency Conversion process with the necessary information to perform the currency conversion that you have previously identified, such as the rule to obtain the appropriate exchange rate, the rule to obtain the subset of dates within which the currency conversion will take place, and the source and target columns for the currency conversion.

See Also

Loading Data Into EPM Foundation