Setting Up Base Currency Conversion Components

This section contains an overview of base currency conversion and provides information about how to set up the basic components required by the PeopleSoft Currency Conversion Utility for converting base currencies including:

• Specifying installation information.

• Creating and assigning work records.

• Identifying exception processes.

• Setting up process groups.

• Defining conversion rules.

Note. Because the Currency Conversion Utility conversion processes are very complex and deal with the conversion of extremely important financial data throughout your system, PeopleSoft strongly recommends that you contact PeopleSoft Global Services (PGS) for assistance in using the Currency Conversion Utility.

Overview of Base Currency Conversion Components

PeopleSoft Currency Conversion Utility uses three basic components for converting base operating currencies.

• Process groups

  The Currency Conversion Utility converts data by process group. Process groups contain conversion rules or exception processes that convert data for one or more products within the same product line.

• Conversion rules

  For each PeopleSoft product with base operating currency data that the Currency Conversion Utility can convert, some PeopleSoft products provide a set of specific conversion rules. If available, PeopleSoft delivers these rules with the Currency Conversion Utility, and you can customize them to fit your business needs.

• Exception processes

  In certain cases, the Currency Conversion Utility supports certain external conversion steps that occur in conjunction with the utility's data conversion. To handle these external conversion processes, the Currency Conversion Utility calls exception processes associated with conversion processes.

Specifying Installation Information

The Currency Conversion Utility requires some fundamental installation information for your site. This section discusses these settings.

Pages Used For Installation Information

Specifying Installed Products

Access the Installed Products page, and make the appropriate modifications.

The Installed Products page is where you specify which products are installed for a particular product line.

If the Currency Conversion Utility encounters a conversion rule owned by a product that is not identified on the Installed Products page as an installed product, and no other installed product identified on this page uses that table specified in the rule, the Currency Conversion Utility bypasses the conversion rule for that table.

The Currency Conversion Utility also bypasses any exception processes for a product that is not specified on the Installed Products page.

Note. The Currency Conversion Utility is always delivered with one product installed: Enterprise Components (PS/EO). It is important to note that this product will not be identified on the Installed Products page. However, the Currency Conversion Utility requires it for conversion processing and you must identify all other installed products on the Installed Products page during setup.

Specifying Installation Options

Access the Installation Options page.

In most cases, you will probably run all of the Currency Conversion Utility conversion processes one at a time using a single machine to drive the conversion. This serial conversion process helps to minimize any processing conflicts or duplications during Currency Conversion Utility conversion. However, if you run the Currency Conversion Utility on two (or more) machines at the same time, you must enable parallel processing before you run any conversion processes.

Warning! PeopleSoft strongly recommends that you do not run the same process group on different machines if you run the Currency Conversion Utility with parallel processing enabled. You risk corrupting your data if you attempt to run the same process group in parallel on multiple machines.

Note. The Currency Conversion Utility runs whether or not parallel processing is enabled.

Creating and Assigning Work Records

The Currency Conversion Utility uses a specific set of temporary tables, or work records, to store and manipulate data during conversion. Depending on how you set up and define conversion processing, the Currency Conversion Utility uses two, three, or all four of these temporary tables during conversion. You associate these temporary work records with the conversion record using the Work Record Assignment page. You can also assign these work records on the Conversion Rule page when you define the conversion rule.

Page Used to Assign Work Records

Creating the Required Work Records

You must create four work records for each Currency Conversion Utility conversion record. These records need the suffixes _TEO1, _TEO2, _TEO3, and _TEOA. _TEOA is the audit record. Depending on how the conversion rule is defined, the Currency Conversion Utility uses two or three of the _TEOn work records to store data temporarily during conversion. The temporary work records are copies of the original record definition with two additional fields added.

This section discusses the processes for creating these work records.

Naming Convention for Conversion Work Records

Currency Conversion Utility work records use the following naming convention:

 [record reference]_TEO[x]

For example, the following work records are associated with the ANALYSIS_GROUP table:

• APPBANK_TEO1

• APPBANK_TEO2

• APPBANK_TEO3

• APPBANK_TEOA

The [record reference] portion of the work record name is user-defined and can contain up to ten characters.

Note. The Currency Conversion Utility requires the _TEO[x] portion of the work record name. This designation is referenced throughout the Currency Conversion Utility's SQL statements and PeopleCode. This designation is a slight variation on the standard TAO naming convention used for PeopleSoft Application Engine temporary work records and helps to clearly identify these work records as those associated with the Currency Conversion Utility.

The Currency Conversion Utility engine uses the TEO1, TEO2, and TEO3 suffixes to determine which temporary record to use to store data during various steps in the conversion process. The TEOA suffix identifies the work record that stores the before-and-after audit details for the conversion record.

Creating TEO1, TEO2, and TEO3

To save time and prevent errors, PeopleSoft recommends that you follow these steps to first create the TEO1 work record from the original conversion record and then clone the TEO2 and TEO3 work records from the TEO1 work record.

To create the TEO1, TEO2, and TEO3 work records:

1. Open the conversion record in Application Designer.

   The conversion record is the record on which the fields reside that you need converted.

2. Select File, Save As, and save the conversion record as a TEOn work record.

   Currency Conversion Utility work record names can have up to ten characters, plus a required four-character _TEOn suffix.

   Note. You do not need to save any PeopleCode on the original record in the TEOn work records.

3. Remove all key field designations from the TEOn work record.

   The field definitions on the TEOn work records must be identical, and they must be in the same order as the fields on the original record.

4. Insert the EO_PROCESS_INST and EO_FROM_CURRENCY fields to the TEOn work record.

   The following two fields must be added to the TEOn work records in the exact location described:

   EO_PROCESS_INST	Must be the first field in the work record definition.
   EO_FROM_CURRENCY	Must be the last field in the work record definition.

5. Specify the EO_PROCESS_INST field as a duplicate order key field on the TEOn work record.

   This field must be the only key on the TEOn work record.

6. Remove any record or field relationship information from the TEOn record properties. Remove any record properties associated with a TEOn record before saving the record definition.

   To remove the record properties from the work record:

   • Open the appropriate record in Application Designer.

   • Click the Properties icon or select File, Object Properties to open the Record Properties for the work record.

   • Select the Use tab, and make sure the record properties of the TEO1, TEO2, and TEO3 record definitions are all blank (particularly the Set Control Field). This does not affect the TEOA record definition.

     Note. Removing these record properties from the TEOn work records is not required for Currency Conversion Utility conversion. However, it does prevent the TEOn work records associated with a conversion record that is part of a Record Group from appearing in system audits as orphan records.

7. Specify the tablespace for the TEOn work record.

   This is required for platforms that use tablespaces. The TEO1 work record uses the CULARG1 tablespace. The TEO2 and TEO3 work records use the corresponding CULARG2 and CULARG3 tablespaces.

   To set the tablespace for the work record, select Tools, Data Administration, Set Tablespace. Select the appropriate tablespace Space Name for the selected work record. Click OK to save the tablespace designation for this work record.

8. Save the TEOn work record.

9. Repeat these steps to create the other two TEOn work records, or clone them from the first.

   Remember to change the tablespace designations on the other two work records regardless of whether you create them individually or clone them from the first work record.

10. Build the TEOn tables using the Application Designer SQL Build utility.

    The Currency Conversion Utility returns an error if the TEOn tables are not built at the time you run the conversion. Data is stored in the TEO1, TEO2, and TEO3 work records only during the actual conversion, so it is safe to build or rebuild the TEOn work records at any time.

    Note. If you modify the original conversion record after you have created the TEOn work records, you must recreate the TEOn records associated with that record to ensure that the modifications are included in the work records.

Creating TEOn Work Records for Records that Contain Subrecords with Key Fields

If you are creating TEO1, TEO2, and TEO3 work records for a conversion record that contains a subrecord with key fields, first clone the subrecord, rename it, and remove the keys. You need to use this cloned subrecord within the primary TEOn records in place of the original subrecord. All the fields within the cloned subrecord must use the same names and remain in the same order as the original subrecord.

Creating the TEOA Audit Detail Record

The TEOA audit detail work record stores the before-and-after conversion details for the fields converted on the conversion record. The field definitions on the Currency Conversion Utility _TEOA work record must be identical to, and in the same order as the fields on the EO_CURRENCY_DTL record. To save time and prevent errors, clone the EO_CURRENCY_DTL record and rename it using the [recname]_TEOA work record naming convention.

To create the TEOA work record:

1. Open the EO_CURRENCY_DTL record in Application Designer.

2. Select File, Save As, and save this record as a TEOA work record.

   We recommend that you use the same naming convention for the TEOA work record that you used for the TEO1, TEO2, and TEO3 work records for the same conversion record. The Currency Conversion Utility requires that the audit detail work record name use a _TEOA suffix.

   You do not need to save any PeopleCode on the original record in the TEOn work records.

3. Specify the tablespace for the TEOA work record.

   This is required for platforms that use tablespaces. The TEOA work record uses the CULARGE tablespace.

   To set the tablespace for the work record, select Tools, Data Administration, Set Tablespace. Select the CUAUDIT space name for the selected work record. Click OK to save this tablespace designation for this work record.

4. Save the TEOA work record.

5. Build the TEOA work record, using the Application Designer SQL Build utility.

   The Currency Conversion Utility returns an error if you have selected an audit processing option on the run control and the TEOA table is not built at the time that you run the conversion.

   Note. Because the TEOA work record is a clone of a Currency Conversion Utility table (EO_CURRENCY_DTL), not the original conversion record, you do not need to rebuild the TEOA table if the original conversion record changes.

Assigning Utility Work Records to Conversion Records

Access the Assign Work Records page.

Note. The PeopleSoft Currency Conversion Utility does not validate the record names when you enter them on this page. This means you can assign work record names to a conversion record before the work records have actually been created. However, work records using the correct structure and using the exact names specified on this page must exist at the time that the record is converted or the Currency Conversion Utility will return an error.

Identifying Exception Processes

Exception processes are product-specific conversion processes (external to the Currency Conversion Utility) that the utility calls at certain exit points during conversion to perform various conversion-related tasks not handled within the logic of the utility.

Understanding Exception Processes

Exception processes are required when field types other than amount, currency code, rate multiplier, and rate divisor fields must be converted, or when conversion-related tasks are required for application tables that cannot be handled by the Currency Conversion Utility.

The Currency Conversion Utility can call exception processes at the process group level or at the conversion rule level. Process group exception processes contain conversion steps that are not record-specific. Conversion rule exception processes relate to a specific database record.

Process group exception processes can run before, after, or in place of all the conversion rules for a process group. Conversion rule exception processes can run before, after, or in place of a specific conversion rule within a process group. You specify the timing and sequencing for an exception process when you associate the exception process with either a process group or a conversion rule.

Note. You can associate both Before and After exception processes with the same conversion rule or process group. However, because In Place Of exception processes are designed to run instead of a conversion rule or a process group, you cannot associate In Place Of exception processes and Before or After exception processes with the same process group or conversion rule.

Exception processes can be PeopleSoft Application Engine programs:

The Currency Conversion Utility calls Application Engine programs directly.

The Currency Conversion Utility calls PeopleSoft Component Interfaces indirectly through a directly-called Application Engine program assigned to a utility conversion process.

If you have to create a new exception process, create it as an Application Engine program or as a Component Interface. You define the calling Application Engine program information on the Exception Process setup page. When the process group runs, the Currency Conversion Utility calls the Application Engine application, which then executes the Component Interface exception process.

In general, exception processes do not do updates or commit any work directly to the database during conversion. When a process group runs, the Currency Conversion Utility uses a run control tracking table to keep a record of all conversion tasks in a process group run, including exception processes. Reasons for using this tracking table include the following:

• A Currency Conversion Utility conversion rule may need the results of conversion-related activity performed by the exception process, or vice versa, during conversion before the update.

• If the Currency Conversion Utility halts conversion prior to the successful completion of an entire process group, the information in this tracking table enables the utility to skip the successfully completed conversion steps in the process group and restart processing at the correct step. In some cases, however, you may want a conversion exception process to always execute, even during restarts. For example, an exception process may perform a particular validation task, without actually making any data updates.

Pages Used to Identify Exception Processes

Identifying Utility Exception Processes

Access the Exception Process page.

The Exception Process setup page populates a Currency Conversion Utility table with information about available exception processes. Once an exception process is added to this table, you can associate it with a process group or a conversion rule. You develop and define exception processes outside the Currency Conversion Utility; however, you must identify them within the utility before you can associate them with process groups or conversion rules.

The exception processes must already exist in the database before you can identify them as a Currency Conversion Utility exception process on this page.

Setting up Process Groups

The Currency Conversion Utility combines related conversion tasks into process groups. Conversion records and tasks can be included in the same process group either because they must all be converted at the same time to maintain data integrity or because they can all be selected using the same selection fields. The Currency Conversion Utility runs one process group at a time.

Understanding Process Groups

The PeopleSoft Currency Conversion Utility uses Process Groups to identify logical groupings of database records that all must be converted at the same time. The Currency Conversion Utility will convert one process group at a time.

In general, you define process groups based on how currency-related data would logically be converted from a business (functional) point of view. Each process group contains conversion criteria that convert currency-related data from a system (technical) point of view.

Each process group contains one or more selection components that identify the field types used to access the records to convert. All the conversion rules within the same process group use the same selection components. The Currency Conversion Utility uses the values of process group selection components as the conversion criteria for the process group. In effect, each selection component for the process group becomes a run control parameter.

Process groups define:

• Selection components for the identifying the record or records to be converted

• Timing for any process group level (non-record specific) exception processes.

Currency Conversion Utility process groups are not limited to a single product. As long as the records selected for conversion within the same database use the same selection components, you have the option to include conversion rules for records in multiple products within the same process group.

Conversely, the Currency Conversion Utility does not require that all records using the same selection components be included in the same process group. Different process groups can use the same selection components. The decision regarding whether to convert records that use the same selection components in the same process group depends on table interdependencies and functional (business) conversion requirements.

Because process groups can convert data across multiple products within the same database, the process group covered products identifies all the products that include conversion rules or exception processes within a single process group.

In some cases, there may be product-specific conversion processes that are not record-specific and that must run in conjunction with a process group. You can associate these process group exception processes with a process group, and the Currency Conversion Utility calls them in their defined sequence when the process group is run.

Pages Used with Process Groups

Setting up Process Groups

Access the Process Group page. The Process Group page provides general identification information for the process group

Dates Allowed	Use to specify which data the Currency Conversion Utility selects for conversion when the process group runs. In some cases, a process group should not convert future or historical data, particularly if there is both effective-dated and noneffective-dated data on the record. Any Date. Selects all records that meet the selection criteria, regardless of date. Current and Future. Selects only current- and future-dated records that meet the selection criteria. Does not select past-dated records. Current and Past. Selects records that meet the selection criteria that have dates up to and including the current date. Does not select future-dated records. Current Date Only. Selects only current-dated records that meet the selection criteria.
Convert Single Currency	Limits a process group so that it converts from a single currency when the process group runs. In certain instances, a process group should be limited so that it converts from a single currency only. For example, if a price list contains items in multiple currencies, you should prevent the Currency Conversion Utility from attempting to convert the same item in multiple currencies to the same currency.
Description	Include requirements for running the process group, such as timing issues, manual processes that must be performed in conjunction with the process group, database status before conversion, and so forth.

Defining Process Group Selection Components

Access the Selection Component page.

The Selection Components page identifies the selection components (run controls) for the process group.

Selection components represent the type of fields the Currency Conversion Utility uses to select the initial subset of rows within the database record to be converted. All the conversion rules within the same process group use the same selection components.

When working with selection components, keep the following in mind:

• Each process group can contain up to ten selection components.

• Every process group must contain a Currency Code selection component, which must be the first selection component in the process group. The value for this currency code will be used as the "from" currency (the pre-conversion currency) on the run control page. The Currency Conversion Utility is able to convert multiple "from" currencies during the same run control—as long as they are all being converted to the same "to" currency.

• At the time the Currency Conversion Utility converts a process group, you will be able to specify whether to convert all the values of a selection component, only those that fall between two values, or only those that equal a specific value.

• Valid selection component data types are Char (character) and Date.

Adding Selection Components to Existing Process Groups

To add a new selection component to an existing process group:

1. Insert a new row in the Selection Components page.

   The Currency Conversion Utility inserts new selection components for process groups with existing conversion rules inserted at the end of the existing selection component list. You can add a new selection component to the middle of the existing process group selection component list only if there are no conversion rules defined for the process group.

2. Enter the details for the selection component.

   Enter the selection component name and the data type.

   Note. If you add a new selection component to an existing process group, you must add selection path information for the field that represents that selection component for the conversion record to all of the conversion rules within that process group. You should also review any exception processes associated with the process group to determine if they need modification.

Deleting Selection Components from Existing Process Groups

You can delete a selection component from a process group using the Process Groups - Selection Component page only under either of the following conditions:

• You have not yet defined any conversion rules for the process group.

• You have removed every reference to the selection component in the selection path for every conversion rule within that process group.

Once you remove all the references to the selection component in the rule's selection path, you can delete the selection component from the process group.

Identifying Process Group Covered Products

Access the Covered Products page. The Covered Products page identifies the database products affected by the process group.

Product

Identify all products that contain conversion rules or exception processes in the process group, including the owner of the process group. Every Currency Conversion Utility process group must have at least one covered product identified.

Note. If you define a conversion rule or exception process for a process group but don't identify the product owner of the rule or exception process as a covered product for that process group, the Currency Conversion Utility does not execute the rule or exception process when the process group runs.

Associating Exception Processes with Process Groups

Access the Exception Processes page.

The Exception Processes page will identify any external exception processes associated with the process group.

When working with exception processes, keep the following in mind:

• The exception process must already exist and be identified on the Exception Process setup page. The product owner of the exception process must be a covered product for the process group.

• A process-group-level exception process can only be assigned to a process group once. There is no limit to the number of exception processes that can be associated with a process group.

Defining Conversion Rules

Use the Currency Conversion Utility's Conversion Rules component to define and maintain the conversion rules associated with a process group.

Overview of Defining Conversion Rules

Conversion rules define the following:

• SQL WHERE clause that the Currency Conversion Utility uses to retrieve the rows that are eligible for conversion within a conversion record.

• Selection path for the record to be converted.

• Table joins for fields on the selected record.

• Fields to be converted on the selected record.

• Reconciliation or adjustment methods for any post-conversion amount discrepancies.

• Timing for running any conversion rule (record-level) exception processes.

All the conversion rules within the same process group use the same selection components, but the names of the fields that represent those selection components may be different on different records within the process group. Field names defined within the conversion rules correspond to the selection components for the process group.

For example, if a process group contains a selection component of Business Unit, a conversion rule would specify the field name on the record (BUSINESS_UNIT) that represents that selection component. You assign field names to all the process group selection components for every conversion rule within the process group. Selection components must be valid for the process group to which the conversion rule belongs.

Note. In certain instances, you may need to include a rule in a process group for a record that does not use all the selection components defined for the process group. While the Currency Conversion Utility allows you to save the conversion rule without all the selection components defined, you receive a warning that selection components are missing whenever you try to save the Conversion Rules component or regenerate the SQL for this product's conversion rules.

If you want to further refine the criteria for determining which rows in the record the Currency Conversion Utility selects for conversion by a rule, you can include additional selection information in the selection path for fields other than selection components.

For example, you may want a conversion rule to select only rows that contain a certain value or have a certain status, but you don't want the field that holds this value to be one of the selection components on the run control. Instead, you can use the selection path to define additional selection specifications that must be met before the Currency Conversion Utility selects a row for conversion. These selection specifications can include specific field values, run control components, or subselects.

The Currency Conversion Utility uses selection path specifications to generate the SQL WHERE clauses for selecting which records to convert. These specifications are stored as parameters for easy maintenance. They are also stored in the SQL repository as portions of SQL statements used in the Currency Conversion Utility's PeopleSoft Application Engine steps and sections.

For effective-dated records, the conversion rule also specifies whether to update the converted row, insert a new effective dated row with no effective sequence number, or insert a new effective-dated row using the next effective date sequence number. The Currency Conversion Utility can also call exception processes associated with a single conversion record when the process group runs. The conversion rule for that record specifies when and how to invoke these rule-level exception processes.

Pages Used with Conversion Rules

Setting up Conversion Rules

Access the Conversion Rules page. The process group ID must already exist. The product owner of the conversion record must be identified as a covered product for the process group.

The Conversion Rules page also identifies any record-specific exception processes that need to be called during the conversion process. The rule will tell the Currency Conversion Utility when and how to invoke these exception processes.

Product	In most cases, the product owner of a conversion rule is the product that owns the record in the database.
	When you save your work on this page, PeopleCode automatically generates corresponding SQL statements and stores them to the SQL repository. Click this button to regenerate the SQL for all the conversion rules and conversion-rule level exception processes for a single product in a process group.
Record	Specify the name of the record converted by the conversion rule.
Description/Long Description	Identify the rule.
Rule Number	A system-generated number uniquely identifying each conversion rule within a process group. The rule number values are sequential, however they do not identify the rule processing sequence. The rule number helps the system distinguish between rules when more than one conversion rule is defined for the same record within the same process group.
Process Seq (process sequence)	Specify in what order to call a conversion rule relative to all the other rules within the same process group. Process sequence numbers do not have to be consecutive as long as they are sequential relative to each other and are unique for each of the conversion rules within the same process group.
Rule Status	Specify whether or not the rule is active. At run time, the Currency Conversion Utility only executes conversion rules with an active status.

Effective Date Handling

This group box provides information about whether a conversion record is effective-dated, and if so, how to handle the conversion for that record.

Work Records

Use the Work Records group box to provide the Currency Conversion Utility with a set of work records it can use to store data temporarily for each record while it's being converted. If you have already created these records in Application Designer and defined these work records using the Work Record Assignment page, the system automatically populates the work record fields for the listed records. If you have not previously specified these work records on the Work Record Assignment page, enter their names on this page; the work records can be specified in either location.

Note. These records must be in place prior to running the conversion process.

Audit Record

Use the Audit Record group box to provide the Currency Conversion Utility with an audit work record it can use to store before-and-after audit detail images for the conversion record. If you have already defined this work record using the Work Record Assignment page, the system populates the audit work record field for this record on this page. If you have not previously identified this audit work record, enter the name of this record.

By default, the Currency Conversion Utility generates a conversion audit trail by capturing before and after images of every conversion field on the conversion record that changed as a result of the conversion. If you want to use this default process for creating an audit trail, leave the Detail Audit check box clear for each rule.

The process group run control page contains a Run All Detail Audits check box that overrides the Detail Audit check boxes for individual conversion rules. If the Run All Detail Audits check box is selected for the process group on the run control, the Currency Conversion Utility generates detail audits for all the conversion rules in the process group, regardless of whether or not the Detail Audit check box is set for an individual rule. If you want to create a detail audit only for a specific conversion record or records, you have to clear the Run All Detail audits check box on the process group run control page and select the Detail Audit check box for each record on the Conversion Rule page. When the process group runs, the Currency Conversion Utility generates an audit trail for the specified conversion records only.

Working with the Execute Product ID or Bypass Product ID Options

Occasionally, when you are creating conversion rules, you may need to specify whether a particular conversion rule should execute if you have a particular product installed. You may also want to include different options for selecting rows in the conversion record if you have a particular product installed. To tell the Currency Conversion Utility to execute a conversion rule only if you have a particular product installed, enter the product in the Execution Product ID field. Alternatively, to tell the Currency Conversion Utility to bypass a conversion rule if you have a particular product installed, enter the product in the Bypass Product ID field.

The Currency Conversion Utility uses a number of factors to determine whether to execute a conversion rule. These factors include the product that owns the conversion record, the execute product, the bypass product, and the impacted products. These factors also include products that have any exception processes associated with the conversion record. For example, there may be two different ways to select rows for the same record, depending on whether you have a particular product installed. You could define one conversion rule with one selection path for the conversion record if you have the product installed. If you do not have that product installed, then you want the Currency Conversion Utility to retrieve the rows using a different conversion rule with a different selection path. To do this, you can define two different rules for the same record, each with different selection paths. In most cases, you don't want the Currency Conversion Utility to execute both rules when the process group runs. To prevent this, you specify on the conversion rule the product that determines whether the Currency Conversion Utility should execute or bypass a conversion rule when the process group runs. The Currency Conversion Utility's criteria for executing or bypassing a conversion rule are the following:

• The owning product and the impacted products are treated as a set.

• If any of the rule's owning or impacted products are installed, the rule is a candidate for execution.

• If you identify an Execute Product ID check box, the Currency Conversion Utility executes the rule only if you have the execute product installed and it is specified as an impacted product for the rule.

• If you identify a Bypass Product ID, the Currency Conversion Utility executes the rule only if you don't have the bypass product installed.

• If you specify both an Execute Product ID and a Bypass Product ID for the same rule, and both products are installed, the bypass option takes precedence and the rule isn't executed.

Example 1: Execute/Bypass Product ID

If these are the product specifications:

Then the rule is executed as follows:

Example 2: Execute/Bypass Product ID

If these are the product specifications:

Then the rule is executed as follows:

Specifying the Selection Path for the Conversion Record

Access the Conversion Rules - Selection Path page. The process group ID must already be defined. The product owner of the conversion record must be a covered product for the process group.

The selection path defines the SQL WHERE clause that the Currency Conversion Utility uses to select rows for conversion for this conversion record. The selection path can include additional parameters for selecting the rows that the SQL statement returns. If a selection component field does not actually reside on the conversion record itself, you can join the other record or records to the selection path using join parameters defined on this page.

For the specified Process Group ID and Product, select the Record for which you want to define a selection path. The system automatically populates the Description and Rule Number fields, based on the selected record.

There may be times when the Currency Conversion Utility returns multiple rows with duplicate key values (resulting in a SQL Cartesian product). To return only one row for each key value, select the Distinct check box to include a DISTINCT in the SQL WHERE clause generated for this conversion rule.

Note. PeopleSoft recommends you use the DISTINCT option only when absolutely necessary because it may adversely affect performance.

Select a Selection Component Name from the prompt list. This list includes only those selection component values that you have defined for the process group.

The And/Or field enables you to include standard Boolean operators in your selection path SQL WHERE clause. The left and right parentheses delineate SQL OR clauses. Select them using the ( and ) check boxes.

If the field for the process group selection component is located on the conversion record, use the Record 1 Name and Field 1 Name fields to identify the record and field name for that selection component.

Use the SQL Operator/Predicate field to compare the Field 1 Name to specific selection or field values. Valid values include the following standard SQL operators and predicates:

If a subselect is required for a field on the Conversion Rules - Selection Path page, select the Subselect Exists? check box and click the activated Subselect button to launch the Subselect page.

If fields on the conversion record derive their values from other records, map the Record 2 Name and Field 2 Name fields to the Record 1 Name and Field 1 Name fields as follows:

You can also use the Conversion Rules - Selection Path page to associate run control components with conversion rule selection specifications, using a value in the Run Control Component Name field. Valid run control component values are %AsOfDate, %CurrentDate, %ProcessInstance, and %ToCurrency.

Values in the Selection Values field represent specific values to which the Field Name 1 is compared using the Operator/Predicate. In order for the Currency Conversion Utility properly to generate the SQL for the conversion rule, enter character values within single quotation marks in the Selection Values field.

Specifying Multiple Selection Values in the Selection Path

If you are specifying more than one character selection value for the same field using the Operator/Predicate IN or NOT IN, enter each value in single quotes and separate them using commas. The Currency Conversion Utility automatically inserts the parentheses when the SQL generates. To compare a Field 1 Name to multiple Selection Values, use commas to separate them. Use single quotes for each character in the field.

Including Subselects in the Selection Path

Access the Subselect page.

The Currency Conversion Utility populates the values in the Process Group ID, Product, Record, Rule Number, Description, Main Select Line Number, Record, Field Name, and Operator/Predicate fields by default, taking them from the Conversion Rules - Selection Path page.

If required, identify the appropriate SQL Function for this subselect. Valid values for the SQL Function field are (none), AVG, MAX, MIN, and SUM.

In the Subselect Recrd (subselect record) field, enter the name of the subselect record. In the Subselect Field, select the appropriate field from the list of fields on the subselect record.

Use the X check box to include an X in your subselect query. If you use an X in your subquery, you do not need to specify a Subselect Field name.

You define the subselect SQL WHERE clause in a way that is similar to the way it is defined on the Conversion Rules - Selection Path page. The And/Or field contains the standard Boolean operators used in SQL statements. The left and right parentheses delineate SQL OR clauses. Select them by selecting the ( and ) check boxes.

Use the Record 1 Name field to specify the subselect record 1 name and use the Field 1 Name field to select the appropriate Field 1 Name from the list of fields on the Record 1 Name.

Use the Operator field to select an operator to compare subselect field values to fields on other records, to specify values for run control component names, or to define specific select values for a field.

Note. Do not use EXISTS or NOT EXISTS as operators when you define the path from the conversion record to the related record. The Currency Conversion Utility does not support subselects for related record joins.

If fields on the subselect record derive their values from other records, map values in the Record 2 Name and Field 2 Name fields to those in the Record 1 Name and Field 1 Name fields.

Select the Of Primary From check box to indicate that the Record 2 Name is the record specified in the primary selection path query, rather than a record specified in the subselect.

You can compare the Field 1 Name in the subselect to a value in the Run Control Component Name field. Valid values for this field are %AsOfDate, %CurrentDate, %ProcessInstance, and %ToCurrency. You can also compare fields to specific selection values in the subselect definition. Enter character selection values using single quotes. Use commas to separate multiple values.

Defining Conversion Fields on Conversion Records

Access the Conversion Rules - Conversion Fields page. The process group ID must already be defined. The product owner of the conversion record must be a covered product for the process group.

The Currency Conversion Utility converts the following Field Categories (types): Amount, Currency, and R(ate) Mult/Div. The page dynamically changes depending on which field category you have selected. If you are defining more than one conversion field on a conversion record for the same conversion rule, add a new row on this page to define the field type and reconciliation or adjustment method for each field.

Defining Amount Conversion Fields

If the value in the Field Category field is Amount, select the amount field name from the list of fields on the conversion record. For amount fields on interrelated tables (such as voucher lines and voucher headers), conversion may result in rounding discrepancies that cause these amounts not to match or balance. To resolve any amount field rounding issues that may arise during conversion, specify a value in the Reconciliation Method field for each amount field and specify the reconciliation record name and reconciliation field name to which the amount field is reconciled.

Note. If you select a Reconciliation Method, Amount Field Name, Reconciliation Record Name, and Reconciliation Field Name field values are required for amount conversion fields. The Currency Conversion Utility returns an error if you try to save this conversion rule without specifying values for these fields.

In the example shown on the Conversion Rules - Conversion Field page above, the conversion record and field (EOCU_ORDER_DET.EOCU_PLANT_PRICE) is being reconciled with the EOCU_ORDER_HDR.EOCU_ORDER_TOTAL record and field. The specified reconciliation method, ConvAdjust (convert and adjust), along with the adjustment method First (largest absolute value), tell the Currency Conversion Utility that once the EOCU_ORDER_DET record is converted, all of the EOCU_PLANT_PRICE rows that are children of the EOCU_ORDER_TOTAL row will have their EOCU_PLANT_PRICE field values summed.

If the sum of the converted record field values doesn't equal the converted value on the related record, the Currency Conversion Utility adds the amount of the discrepancy to the converted record amount, which is the first in the record.

Amount field category Reconciliation Methods include the following:

If you specify a reconciliation method that requires the amount of one of the rows in a series to be adjusted (ConvAdjust or AdjustOnly), you also have to specify a value in the Adjustment Method and Additional Key Field fields.

The Currency Conversion Utility provides the following amount Adjustment Method field values:

If you select either the First or Last as the Adjustment Method for reconciling an amount field, the Additional Key Field uniquely defines each record in the series and must be a number field. If you select any of the other adjustment methods, use the Additional Key Field to select the record to be adjusted if there is more than one row selected with the same amount.

Defining Currency Code Conversion Fields

For the Field Category field value of Currency, select a value for the Currency Field Name field from the available list of fields on the conversion record.

Defining Rate Multiplier and Rate Divisor Conversion Fields

For the Field Category field value of R Mult/Div (rate multiplier or rate divisor), enter the rate multiplier field in the Rate Multiplier Field Name field, and the rate divisor field in the Rate Divisor Field Name field. Select from the available number and signed number fields on the conversion record.

The Rate Multiplier and Rate Divisor exchange rate fields require that you identify the name of both field types and which currency uses these field values (the currency converted from or the currency converted to).

In general, the Rate Multiplier and Rate Divisor fields are only converted as a result of a corresponding currency code being converted. The options in the Currency Direction group box indicate whether the currency code being converted is the From Currency or the To Currency for the rate multiplier and rate divisor pair. The Currency Conversion Utility returns an error message if either the Rate Multiplier or Rate Divisor field contains a value of zero for any of the From currencies at run time.

See Understanding Exchange Rate Conversions (Rate Multiplier and Rate Divisor).

Defining Join Parameters for Amount Conversion Fields

Access the Join Parameters page.

The Join Parameters page provides information about how to join the conversion record to the related reconciliation record. The example above represents the following SQL WHERE clause:

Enter the Record 1 Name and Field 1 Name from the conversion record and the related fields on the related record using the Record 2 Name and Field 2 Name fields. For each field that you join, enter the appropriate Operator. If additional fields are required to join the conversion record to the related record, add the field and record names and specify any Selection Values.

Note. Do not use EXISTS or NOT EXISTS as operators when you define the path from the conversion record to the related record. The Currency Conversion Utility doesn't support subselects for related record joins.

You can also compare a Field 1 Name to a specific selection value. Enter character values using single quotes. Separate multiple values with commas. The selection values for join parameters are similar to those for the conversion rule selection path.

Associating Exception Processes with Conversion Rules

Access the Conversion Rules - Exception Processes page. The exception process must already exist and be identified on the Exception Process setup page. The product owner of the exception process must be a covered product for the process group.

Occasionally, converting a particular conversion record may involve logic that cannot be included within the conversion rules. In addition, the Currency Conversion Utility may have to modify other related records when a particular conversion record is converted. To handle this record-specific logic, you can associate exception processes with specific conversion records. When the process group runs, the Currency Conversion Utility calls these record-specific exception processes before, after, or in place of the conversion rule for that conversion record.

Note. For Before Conversion Rule and After Conversion Rule exception processes, the Currency Conversion Utility creates audit trail data for the conversion fields defined in the conversion rule. For In Place Of Conversion Rule exception processes, no audit process occurs.

Identifying Products Impacted by Conversion Rules

Access the Conversion Rules - Impacted Products page. The product owner of the conversion must be a covered product for the process group.

Note. An impacted product is one that uses the conversion record specified on the conversion rule. A covered product is one that has defined conversion rules or exception processes for a particular process group. An impacted product may or may not be identified as a covered product for the process group. An installed product is one that is installed on the database.

Reviewing Process Group Details

The Currency Conversion Utility provides several inquiry pages that you can use to review details about conversion rules and exception processes for each process group.

Pages Used to Review Process Group Details

Using the Conversion Rules Inquiry

Access the Rules page.

The process group and conversion rules must already be defined.

Select a Process Group ID from the list of valid values. To narrow the scope of the inquiry, enter Product ID, From Proc Seq (from process sequence), and To Proc Seq (to process sequence) values.

If you want to see all the rules for a particular process group, enter only the Process Group ID value.

Once you've selected your parameters, click the Load Process Group Rules button to display the following information about the process group.

Viewing Conversion Field Details

Access the Conversion Field Detail inquiry page.

The display-only Conversion Field Details page includes information on each field defined on the conversion record. This online inquiry report includes the name of each field converted, what type of field it is, the currency direction (for Rate Multiplier and Rate Divisor fields only), whether there is any reconciliation or adjustment method and related records and fields defined, and the Field SQLID number for the conversion field.

Viewing Conversion Rule Exception Process Details

Access the Rule Exception Processes inquiry page.

The Rule Exception Processes inquiry page displays the details for any record-level exception processes associated with the conversion rule. Information on this page includes the name and description of the exception process and timing and sequence for the exception process.

Viewing Conversion Rule Selection Path Details

Access the Selection Path Details inquiry page.

The conversion rule Selection Path Details inquiry page displays the selection path defined for the conversion record. The information on this page defines the SQL WHERE clause used by the Currency Conversion Utility at run time to select the rows on the conversion record that are candidates for conversion when the process group is run. Information included on this path includes all the information defined on the Selection Path page for this conversion record. This online inquiry page does not display details for subselects defined in the selection path.

Using the Conversion Exception Process Inquiry

Access the Review Process Group - Exceptions page.

You must complete the Conversion Rules Details page first.

Select a Process Group ID from the list of valid values. To narrow the scope of the inquiry, you can enter Product ID, From Proc Seq (from process sequence), and To Proc Seq (to process sequence) values.

If you want to see all of the exceptions processes for a particular process group, enter only the Process Group ID value.

Once you've selected your inquiry parameters, click the Load Process Group Rules button to view the inquiry results.

This inquiry view includes the ID of the product that owns the exception process, the name and description of the exception process, and timing and sequencing information.