Final Implementation Guide

PeopleSoft General Ledger 9.
1 Integration to
Oracle® Fusion Accounting Hub 1.0.1
Implementation Guide
November 2011
PeopleSoft General Ledger 9.1 Integration to Oracle® Fusion Accounting Hub 1.0 Implementation Guide October 2011
PeopleSoft GL to Financials Accounting HubCopyright © 2011, Oracle and/or its affiliates. All rights
reserved.
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in
your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free.
If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be
subject to the restrictions and license terms set forth in the applicable Government contract, and, to the
extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-
19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle
Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.
Oracle Proprietary and Confidential ii

Table of Contents
Chapter 1................................................................................................................................................. 3
Understanding the Integration of PeopleSoft General Ledger to Fusion Accounting Hub........3
PeopleSoft GL to Fusion Accounting Hub Integration Overview.......................................................3
Common Terminology Used in the PeopleSoft to Fusion Integration................................................4
Prerequisites and Considerations..................................................................................................... 5
Chapter 2................................................................................................................................................. 7
Implementing the PeopleSoft General Ledger to Fusion Accounting Hub Integration.............7
34BOverall Integration Implementation Setup and Process Flow.....................................................8
33B17B13B PeopleSoft Pages Used in the Fusion Accounting Hub Integration.............................9
Records Used in the PeopleSoft to Fusion Accounting Hub Integration.........................................10
32B21B20B14BHigh-Level Integration Implementation Checklist................................................11
2BChapter 3........................................................................................................................................... 12
Configuring Oracle Data Integrator (ODI) for the Fusion Accounting Hub Integration............12
Performing Post-Installation Steps 110H(return to checklist)...........................13
Importing ODI Integration Artifacts 111H(return to checklist)...............................18
37BUpdate the Schema and Work Schema Names in the Data Server Setup...............................21
Launching the GL_SET_FUSION_USER scenario.........................................................................22
Chapter 4............................................................................................................................................... 23
Setting Up PeopleSoft General Ledger for the Fusion Accounting Hub Integration...............23
Updating Permission List for Access 126H(return to checklist).................................24
30BMapping PeopleSoft System ID and Transfer ID 127H(return to checklist).......................25
24BMapping Source to Target Language.......................................................................................25
1BMapping PeopleSoft and Fusion Account Types 129H(return to checklist)......................26
28BMapping PeopleSoft ChartFields to Fusion Segments 131H(return to checklist)..................27
29BMapping SetID and ChartField Combinations to Fusion Value Set Codes
132H(return to checklist)................................................................................................................ 28
26BMapping PeopleSoft Ledgers to Fusion Ledgers 137H(return to checklist)........................30
27BMapping Adjustment and Closing Periods 139H(return to checklist).............................32
36BTransforming PeopleSoft Journals to Fusion Journals 141H(return to checklist).................34
8BDrilling Back from Fusion Accounting Hub Journals to PeopleSoft Journals..............................36
Chapter 5............................................................................................................................................... 38
Configuring Fusion for the PeopleSoft GL to Fusion Accounting Hub Integration..................38
35B12BRegistering Apps Unlimited Instances 165H(return to checklist).............................40
Oracle Proprietary and Confidential 1

PeopleSoft General Ledger 9.1 Integration to Oracle® Fusion Accounting Hub 1.0.1 Implementation Guide November 2011
Verifying Fusion Account Types...................................................................................................... 41

Defining Target Value Sets for Corresponding PeopleSoft ChartFields...........................................41
Defining the Accounting Flexfield (Chart of Accounts)....................................................................42
Setting Up Calendars and Opening Accounting Periods for the Ledgers........................................43
Creating Target Ledgers in Fusion Accounting Hub........................................................................44
Initiating Transaction Processing and Verifying Results..................................................................45
Reviewing the Fusion Journals and Drilling Back to PeopleSoft Source Journals..........................46
Appendix A............................................................................................................................................. 47
ODI Model Folder Artifacts for PeopleSoft GL to Fusion Accounting Hub Integration............47
Appendix B............................................................................................................................................. 48
ODI Project Artifacts for PeopleSoft GL to Fusion Accounting Hub Integration......................48
Appendix C............................................................................................................................................ 50
PeopleSoft Journal Staging Record.......................................................................................50

Chapter 1
Understanding the Integration of PeopleSoft General
Ledger to Fusion Accounting Hub
This chapter provides an overview of the integration between Fusion Accounting Hub 1.0.1 and
PeopleSoft General Ledger (GL) 9.1 and describes:
Common terminology used in this integration.
Prerequisites and considerations.
PeopleSoft GL to Fusion Accounting Hub Integration Overview

Oracle provides the ability for PeopleSoft General Ledger 9.1 users to integrate with Oracle Fusion
Accounting Hub. As such, PeopleSoft GL users can take advantage of Fusion Accounting Hub features,
such as the embedded Hyperion Essbase features, and the ability to create accounting transformations
for diverse industry-specific source systems, while continuing to use PeopleSoft General Ledger as the
system of record.
After configuring the delivered setup pages, you can transform and transfer PeopleSoft General Ledger
journals to Fusion General Ledger journals and leverage the analysis and reporting tools within Oracle’s
Fusion Accounting Hub. This document describes the integration process and the configuration of the
applications that are involved in the implementation of this integration.
This integration enables you to perform the following functions:
 Map PeopleSoft control data such as business units and ledgers to Fusion ledgers.
 Upload and convert chart of accounts data from PeopleSoft to Fusion.
 Transfer journals from the PeopleSoft General Ledger to the Fusion General Ledger.
 Drilldown from Fusion journal line detail to PeopleSoft journal details.
Delivered as part of the integration between Fusion Accounting Hub and PeopleSoft GL are:
1. 45H Oracle Data Integrator (ODI) artifacts with which to process the integration.
2. PeopleSoft Component to store the System ID with the Transfer ID that is used to populate these
46H
fields in the integration tables. See Records Used in the PeopleSoft to FAH GL Integration.
47H
3. PeopleSoft Components to map Account Type values and Language Codes between the systems.
48H
4. PeopleSoft Component to map PeopleSoft ChartFields to Fusion Segments.

49H
5. PeopleSoft Component to map setID and ChartField combinations to Fusion Value Set Codes.
50H
6. PeopleSoft Component to map business unit and ledger combinations to Fusion ledgers.
51H
7. PeopleSoft Component to map adjustment and year-end closing periods between applications.
52H
8. PeopleSoft Run Control that transforms and stages PeopleSoft initial ledger balances and posted
53H
journal data for transfer to Fusion General Ledger. The ODI process transfers the data from
Peoplesoft to Fusion.
9. 54H Drillback capability from Fusion Accounting Hub inquiry to a new Journal Lines drillback page in

PeopleSoft with a link to the Review Journal Status component.
Common Terminology Used in the PeopleSoft to Fusion Integration
The following terms are commonly used in the integration between PeopleSoft GL and Fusion:
Term Definition
COA COA refers to the chart of accounts structure (also known as the Accounting
Flexfield in Oracle applications and the ChartField structure in PeopleSoft
applications). It is the underlying foundation that is used to categorize, track and
report accounting information that resides in the general ledger.
Fusion Accounting Oracle Fusion Accounting Hub is an application that can be used as an
Hub (FAH) integration and reporting platform. It includes functionality for transforming
information from non-Oracle source systems into detailed, auditable accounting.
It also includes a reporting platform, with embedded Hyperion Essbase
functionality and Financial Reporting Studio to create multi-dimensional financial
reporting. Fusion Accounting Hub includes integration to EBS General Ledger,
PeopleSoft General Ledger, and Hyperion Data Relationship Management.
ODI Oracle Data Integrator (ODI) is the vehicle through which transactions are
transformed and transferred from PeopleSoft GL (or other applications) to Fusion
Accounting Hub.
Segments (Fusion Segments represent dimensions for a chart of accounts. They are the Fusion
Flexfield equivalent to PeopleSoft ChartFields. Segments, just as ChartFields, are used to
Segments) categorize financial or statistical data to record transactions to ledgers or
subledgers for the ultimate purpose of meeting reporting requirements. Examples
of segments include Company, Department, Account, Subaccount, and so on.
SetID The setID is a component of PeopleSoft architecture that allows you to share
data across entities and align certain static data to specific entities. Static data
such as calendars can be globally shared among entities while departments for
different countries, for example, can be specifically assigned using a different
setID.
Value Set Value sets are used to maintain all the valid values of a dimension for the chart of
accounts. Each segment in the chart of accounts must have an associated value
set. For example, a value set of "Account" could be used to hold all the possible
values that can be used for the account segment of a chart of accounts. Value
sets are the Fusion equivalent to the PeopleSoft combination of setID and
ChartField.

Prerequisites and Considerations

The following section discusses prerequisites and considerations to review prior to implementing the
integration between Fusion Accounting Hub and PeopleSoft GL:
Prerequisites
The following are prerequisites for implementing the PeopleSoft GL to Fusion Accounting Hub integration:
PeopleSoft 9.1 GL is installed and PeopleSoft Financials Resolution ID 872183 is applied. All initial
setup tasks must be completed. For PeopleSoft setup tasks, see Setting Up PeopleSoft General
55H
Ledger for the Fusion Accounting Hub Integration.
Fusion Accounting Hub 1.0.1 is installed and all initial setup tasks are completed. To view the list of
initial setup tasks for Fusion Accounting Hub, see Configuring Fusion Accounting Hub for the
56H
PeopleSoft GL to Fusion Accounting Hub Integration. This section includes references to

documentation of Fusion Accounting Hub setup. For more information, see Oracle Fusion Accounting
Hub Implementation Guide.
Oracle Data Integrator (ODI) must be installed and configured (11.1.1.5.0). Download the ODI
integration artifacts. See Configuring Oracle Data Integrator (ODI) for the Fusion Integration.
57H
Fusion Accounting Hub operates exclusively on the Oracle database platform.
Considerations
Consider the following differences when mapping data between PeopleSoft GL and Fusion GL:
PeopleSoft shares ChartField information via setID and business unit whereas Fusion shares value
set definitions across chart of accounts (COA) structures, which are associated with ledgers.
Fusion COA values can each have an Enabled flag and an active effective date range, but it is
different from PeopleSoft’s concept of Active or Inactive status and multiple effective-dated rows.
Therefore, you cannot map future-dated rows from PeopleSoft GL to Fusion Accounting Hub.
InterUnit journals from PeopleSoft are transferred as separate journals by business unit.
Affiliate fields cannot be mapped from PeopleSoft to Fusion. If you are using the Affiliate (Direct)
method for interunit processing in PeopleSoft, you may need to consider recording your interunit
amounts that are differentiated by Affiliate into separate accounts (Indirect method) to designate the
concatenated Account-Affiliate combination.
If you would like to perform Allocations, Consolidations, and InterUnit processing in Fusion instead of
within PeopleSoft, you must set up the respective processing rules within Fusion.
Alternate account relationships are not stored in the Fusion Accounting Hub. Multi-GAAP accounting
can be created in the Fusion Accounting Hub with multi-GAAP ledgers rather than using alternate
accounts.
Fusion GL does not use the ledger group concept. PeopleSoft ledgers that are grouped in the same
ledger group (multibook) are represented in Fusion Accounting Hub as separate ledgers. Use the
Fusion primary ledger and the associated reporting ledgers (within the context of a PeopleSoft
business unit) to map to PeopleSoft multibook ledgers.

You must manually create, maintain, and synchronize chart of accounts structures in Fusion GL that
replicate the ChartFields that are used in PeopleSoft GL. These tables should contain and mirror the
PeopleSoft COA values so that as values are added in PSFT they are automatically available in
Oracle.
You must manually create, maintain, and synchronize the Fusion ledgers that correspond to the
PeopleSoft ledgers.
You must manually create accounting calendars in the Fusion Accounting Hub. The journal date of
the Peoplesoft journal determines the accounting period in Fusion. There is no mapping between
Peoplesoft GL accounting periods and the Fusion Accounting Hub. The only period mapping is for the
adjustment and year-end closing periods.
Run a process to populate the Fusion Value Sets with the corresponding PeopleSoft ChartField
values only one time per PeopleSoft database instance. You run this process during the integration
implementation. Thereafter, when new values are added, you must manually maintain and
synchronize the values between the systems.
You must manually synchronize and maintain trees in both PeopleSoft and Fusion.
Fusion requires that all fields be populated to successfully generate journals. Therefore, unlike
PeopleSoft journals, you cannot selectively populate ChartField values. Ledger data may be thicker
as a result; however, this avoids a restructuring of fields when posting. The standard migration
updates all blanks in GL_XFR_PSFT_RAW_INT (interface table in Fusion) with defaults specified for
the respective fields before the journal import runs.
This integration does not deliver a service for synchronizing currency exchange rates between the
applications. If this is a requirement, you can manually synchronize or write a program to
accommodate the requirement.
In order for the transfer of journals to work properly for this integration, the PeopleSoft ledger and its
corresponding Fusion ledger must have the same functional currency.
If you want to revalue historical ledger balances, you must enter the currency rates in Fusion GL.
This integration does not deliver a service for synchronizing ChartField combination rules between
the applications. If this is a requirement, you can manually create cross validation rules in the Fusion
Accounting Hub. If you want consistent validations between Peoplesoft GL and Fusion Accounting
Hub, you can manually replicate the validations using the functionality offered by each application.
If you want to create translation ledgers, you must run the translation process directly in Fusion GL for
the migrated historical balances.

Chapter 2
Implementing the PeopleSoft General Ledger to
Fusion Accounting Hub Integration
This chapter presents the process flow of the integration and includes the following topics:
58H Overall Integration Implementation Setup and Process Flow.
59H PeopleSoft Pages Used in the Fusion Accounting Hub Integration.
60H Records Used in the PeopleSoft to Fusion Accounting Hub Integration.
61H Implementation Methodology – Overall Integration Checklist.
The implementation methodology is intended to provide a preliminary blueprint for step-by-step

implementation of the integration. The details will vary depending upon each implementation’s situation
and specific requirements but provides a basic guideline as a starting point.

34B Overall Integration Implementation Setup and Process Flow

The following is a high-level flow of the PeopleSoft GL to Fusion Accounting Hub integration:
1. Map control data, such as PeopleSoft setID and ChartField combinations to Fusion Value Set Codes,
corresponding Ledger, Calendar/Accounting periods, and Chart of Accounts information between the
PeopleSoft and Fusion applications.
2. Use the run control (Application Engine program) to transform the PeopleSoft initial ledger balances
and journals, accessing the mapped control data and populating rows in a staging table that are
transferred to Fusion Accounting Hub (General Ledger).
3. Oracle Data Integrator (ODI) performs the data transfer from PeopleSoft to Fusion and submits the
PeopleSoft Import and Transform program in the Fusion database.
4. Within the Fusion database, the PeopleSoft Import and Transform program validates the rows in the
staging table. If the data passes validation, this program converts the ChartField values to Fusion
chart of accounts values, if necessary, and submits the Fusion Journal Import program to create the
corresponding Fusion journals. If the data fails validation, the Import and Transform program does
not launch the Fusion Journal Import program; instead, it produces an execution report describing the
errors. The Fusion Journal Import program performs additional validations and creates journals.
Below is a high-level flow of the integration between PeopleSoft and Fusion Accounting Hub:

33B17B13B PeopleSoft Pages Used in the Fusion Accounting Hub Integration

The following pages are used in the PeopleSoft General Ledger to Fusion Accounting Hub integration:
Page Object Name Navigation Usage

Name
Setup
62H FUS_SETUP_OPT General Ledger, Fusion Accounting Includes values for System ID and Transfer ID,
Options Hub, Setup Options, Setup Options which populate the integration tables as
unique identifiers representing the PeopleSoft
database instance and transfer process
instance, respectively.
Language
63H FUS_INSTALL_ General Ledger, Fusion Accounting Map source PeopleSoft language to target
Mapping LNG Hub, Language Mapping, Language Fusion language.
Mapping
Account
64H FUS_ASGN_ General Ledger, Fusion Accounting Map Account Type values between PeopleSoft
Type ACCTYPE Hub, Account Type Mapping, Account and Fusion.
Mapping Type Mapping
ChartField /
65H FUS_CFSEGMENT General Ledger, Fusion Accounting Map PeopleSoft ChartFields to Fusion
Segment _MAP Hub, ChartField/Segment Mapping, Segments.
Mapping ChartField / Segment Mapping
Value Set
66H FUS_ASGN_CFVS General Ledger, Fusion Accounting Map the PeopleSoft setID and ChartField
Mapping Hub, Value Set Mapping, Value Set combinations to the Fusion Value Set Codes.
Mapping Run the FUS_CFANLYZR process to initially
load the Value Set staging table that is used in
the data transfer from PeopleSoft to Fusion.
Ledger
67H FUS_LEDGER_ General Ledger, Fusion Accounting Map the PeopleSoft Business Unit and Ledger
Mapping UIMAP Hub, Ledger Mapping, Ledger combinations to Fusion Ledger and COA
Mapping Mapping Name combinations. View the status
of the transfer process by Transfer ID.
Adjustment
68H FUS_PERIOD_ General Ledger, Fusion Accounting Map calendar and adjustment periods
/Closing MAP Hub, Adjust/Closing Period Mapping, between PeopleSoft and Fusion for
Period Adjustment/Closing Period Mapping transaction processing and reporting.
Mapping
Transform/
69H FUS_PSJRNL_ General Ledger, Fusion Accounting Run the process to transform PeopleSoft
Stage GL TRANS Hub, Transform/Stage GL Journals, journals and stages them for transfer to Fusion
Journals Transform/Stage GL Journals (FUS_PSJRNLTR Application Engine
process). Also use this process to load initial
ledger balances.
Journal
70H FUS_DRILLBACK_ General Ledger, Fusion Accounting Access this page to view transferred journals
Line JRNL Hub, Journal Line; or, from PeopleSoft to Fusion and drill down to

Page Object Name Navigation Usage

Name
Drill back from Fusion Accounting the journal details.

Hub application inquiry.
Records Used in the PeopleSoft to Fusion Accounting Hub Integration

The following table lists some of the key records that are used in the integration between PeopleSoft
General Ledger and Fusion Accounting Hub:
Record Name Description Usage
FUS_GL_XFR_INTF PeopleSoft Journal Transfer Fusion interface staging table within Peoplesoft
(ODI then transfers data from Interface Table for Fusion that contains the mapped journal data to be
this PeopleSoft record to the Accounting Hub and Peoplesoft transferred by Oracle Data Integrator (ODI) to
Fusion integration record, General Ledger integration Fusion General Ledger. Populated by the
GL_XFR_PSFT_RAW_INT) FUS_PSJRNLTR Application Engine processes.
71H
FUS_CFVS_MAP Value Set mapping table Maps PeopleSoft setID and ChartField
combinations to Fusion Value Set codes.
Populated by the Value Set Mapping page.
72H
FUS_LEDGER_MTBL Ledger mapping table Maps PeopleSoft Business Unit and Ledger
combinations to Fusion Ledger and COA
Mapping Name combinations. Populated by
Ledger Mapping page.
73H
FUS_ACCTYPE_MAP Account type mapping table Map Account Type values between PeopleSoft
and Fusion. Populated by Account Type 74H
Mapping page.
FUS_PERIOD_MAP Calendar and adjustment period Maps calendar and adjustment periods between
mapping table PeopleSoft and Fusion for transaction and
transfer processing and reporting. Populated by
the Adjustment/Closing Period Mapping page.
75H
FUS_CFSEG_MAP ChartField to Segment mapping Maps PeopleSoft ChartFields to Fusion

table Segments. Populated by ChartField / Segment
76H
Mapping page.
FUS_INSTALL_LNG Language code mapping Maps source language code to target language
code. Populated by Language Mapping page.
77H

32B21B20B 14B High-Level Integration Implementation Checklist

The following provides a high-level guideline for the implementation tasks:
Task Task Responsible

(link to documentation) Application
0.1 Installation and Configuration

0.1.1 PeopleSoft GL Configuration:
 PeopleSoft GL 9.1 is installed and configured.
 Resolution ID 872183 is applied. PeopleSoft
0.1.2 Install Fusion Accounting Hub 1.0.1
78H Fusion
Configuring Oracle Data Integrator (ODI) for the Fusion Accounting Hub
79H ODI
0.1.3 Integration
ODI Model Folder Artifacts for PeopleSoft GL to Fusion Accounting Hub
80H ODI
0.1.4 Integration
ODI Project Artifacts for PeopleSoft GL to Fusion Accounting Hub
81H ODI
0.1.5 Integration
1.0 Register Applications
1.1 Registering Apps Unlimited Instances
82H Fusion
1.2 Updating Permission List for Access
83H PeopleSoft
1.3 Mapping PeopleSoft System ID and Transfer ID
84H PeopleSoft
2.0 Map Source to Target Control Data
2.1. Mapping Source to Target Language
85H PeopleSoft
2.2.1 Mapping PeopleSoft and Fusion Account Types
86H PeopleSoft
2.2.2 Verifying Fusion Account Types
87H Fusion
2.3.1 Mapping PeopleSoft ChartFields to Fusion Segments
88H PeopleSoft
2.3.2 Defining the Accounting Flexfield (Chart of Accounts)
89H Fusion
2.4.1 Setting Up Calendars and Opening Accounting Periods for the Ledgers
90H Fusion
2.4.2 Mapping Adjustment and Closing Periods
91H PeopleSoft
2.6.1 Creating Target Ledgers in Fusion
92H Fusion
2.6.2 Mapping PeopleSoft Ledgers to Fusion Ledgers
93H PeopleSoft
2.7.1 Defining Target Value Sets for Corresponding PeopleSoft ChartFields
94H Fusion
2.7.2 Mapping SetID and ChartField Combinations to Fusion Value Set Codes
95H PeopleSoft
2.7.3 Process Initial Load of Value Sets from PeopleSoft to Fusion
96H PeopleSoft
3.1 Transfer Journals from PeopleSoft GL to Fusion Accounting Hub
3.1.1 Transforming PeopleSoft Journals to Fusion Journals
97H PeopleSoft
3.1.2 Initiating Transaction Processing and Verifying Results
98H Fusion
Reviewing the Fusion Journals and Drilling Back to PeopleSoft Source
99H Fusion
3.1.3 Journals
Drilling Back from Fusion Accounting Hub Journals to PeopleSoft
100H Peoplesoft
3.1.4 Journals

2B Chapter 3
Configuring Oracle Data Integrator (ODI) for the
This chapter provides an overview of ODI and discusses the following topics:
 Prerequisites and Requirements
 Performing post-installation steps and importing ODI artifacts
The ODI ELT tool must be installed and configured properly in order to transform PeopleSoft journals into
mapped Fusion journal lines and transfer those journal lines from the PeopleSoft journal staging record
(FUS_GL_XFR_INTF) to the Fusion journal staging record (GL_XFR_PSFT_RAW_INT).
Prerequisites and Requirements 101H (return to checklist)
ODI 11.1.1.5.0, on Windows or Linux only, is used to transport the journal lines from the PeopleSoft
staging table to the Fusion Accounting Hub staging table. ODI 11.1.1.5.0, on Windows or Linux,
should be installed with featured components like Standalone Agent, ODI Studio, Java EE, ODI
Console and Web Service.
Web Logic Server is also used.
Upgrade ODI to 11.1.1.5.0 by installing the latest patch. The patch may be installed for ODI versions
10.1.3.4.0 and above. To check your version of ODI, open Designer and select Help, About Oracle
Data Integrator menu. The version appears in the About window.
For preinstallation and installation steps, which include configuring properties and installing the
patches, see the Oracle Installation and Upgrade Guide. The master and work repositories already
exist within the delivered Fusion Accounting Hub.
Performing Post-Installation Steps and Importing ODI Artifacts

This section describes the following post-installation steps:
1. 102H Create data servers for source and target databases through ODI Console.
2. 103H Create physical schemas for source and target databases through ODI Console.
3. 104H Create the context code.
4. 105H Create logical schemas for source and target databases.
5. 106H Import Model Folder using command-line instructions.
6. 107H Import Model and Project files using command-line instructions.

7. 108H Update the schema and work schema names in the data server setup (established in step 1).
8. 109H Launch the GL_SET_FUSION_USER scenario.
Note: It is important to complete the mandatory field values exactly as indicated in the steps that follow
for the successful import of the ODI models and project.

Performing Post-Installation Steps 110H (return to checklist)
4B Create Data Servers for Source and Target Databases through the Oracle Data Integrator Console:
.1 Connect to the Master Repository and from the Browse Tab, expand the Topology folder.
.2 Right click on Data Servers:
.3 Select Create and set up your Data Server connection information for both the source database (PeopleSoft)
and the target database (Fusion) as follows:
Field Values for PeopleSoft (Source Database) Comments
Data Server Name ORACLE_PEOPLESOFT_FAH Mandatory Value
Technology ORACLE Select platform of your PeopleSoft

installation.
Batch Update Size 30 Use default value
Array Fetch Size 30 Use default value
JDBC Driver oracle.jdbc.OracleDriver Select applicable JDBC driver for your

installation.
JDBC URL jdbc:oracle:thin:@<host>:<port>:<SID> Provide the connection information.
User and Password <UserID> Supply appropriate user ID and password

as defined by the implementation team for
<Password>
access to the PeopleSoft (source) database.

Field Values for Fusion (Target Database) Comments
Data Server Name ORACLE_FUSION_FAH Mandatory Value
Technology ORACLE Fusion only works on Oracle platform.
Batch Update Size 30 Use default value
Array Fetch Size 30 Use default value
JDBC Driver oracle.jdbc.OracleDriver Select applicable JDBC driver for your

installation.
JDBC URL jdbc:oracle:thin:@<host>:<port>:<SID> Provide the connection information.
User and JDBC <UserID> = fusion The User ID value for the Fusion (target
Password database) is fixed as “fusion.” The password is
<Password> = <user-defined>
defined by the implementation team or user.
.4 Save each data server connection configuration.

.5
6B Create Physical Schemas for Source and Target Databases through the Oracle Data Integrator Console:
.1 Expand the Schemas folder and right click on Physical Schemas:

.2 Select Create and access the Data Server that you created in the previous section.
.3 Enter the database schema name, if applicable.
.4 Configure the Physical Schema for Peoplesoft (Source Database) for Data Server,
ORACLE_PEOPLESOFT_FAH as follows:
Field Values for PeopleSoft (Source Database) Comments
Physical Schema (This field populates automatically once you select

Name the data server)
Data Server ORACLE_PEOPLESOFT_FAH Select from drop-down list.
Schema Name (leave blank) Complete this field only after completing the
import step. Until then, leave field blank.
Work Schema Name (leave blank) Complete this field only after completing the
Catalog (leave blank)
Catalog Name (leave blank)
Default Select Select to make this the default.

.5 Save.
.6 Configure the Physical Schema for Fusion (Target Database) for Data Server, ORACLE_FUSION_FAH as
follows:
Field Values for Fusion (Target Database) Comments
Physical Schema (This field populates automatically once you select

Name the data server)
Data Server ORACLE_FUSION_FAH Select from drop-down list.
Schema Name (leave blank) Complete this field only after completing the
Work Schema Name (leave blank) Complete this field only after completing the
Catalog (leave blank)
Catalog Name (leave blank)
Default Select Select to make this the default.
.7 Save.
3B Create Context Code = DEVELOPMENT_FAH
.1 Right click the Contexts folder, select Create and enter the following:
Field Values Comments
Context Code DEVELOPMENT_FAH Mandatory Value
Context Name Development_fah Mandatory Value
Default Context Select Select to make this the default.
.2 Save.

5B Create Logical Schemas for Source and Target Databases
.1 Expand the Schemas folder, click on Logical Schemas folder and select Create. Create a logical schema, for the
Peoplesoft database and another schema for the Fusion database:
Logical Schema ORACLE_PSFTFSCM Mandatory Value

Name
Technology ORACLE Select platform of your PeopleSoft installation.
.2 Save.
.3 Click on ORACLE_PSFTFSCM to edit the context information. For the context, DEVELOPMENT_FAH, select
the physical schema, ORACLE_PEOPLESOFT_FAH.
.4 Create the logical schema for the Fusion database. Click on the Logical Schemas folder and select Create:
Logical Schema ORACLE_FUSION Mandatory Value

Name
Technology ORACLE Fusion platform can only be Oracle.
.5 Save.
.6 Click on ORACLE_FUSION to edit the context information. For the context, DEVELOPMENT_FAH, select the
physical schema, ORACLE_FUSION_FAH.

Importing ODI Integration Artifacts 111H (return to checklist)
Once you have performed all of the post-installation steps as outlined in the previous section, you can
import the ODI projects using command lines. If you encounter repository or connection-related issues,
check the odiparams.bat and review your connectivity and login settings.
Note: The following steps assume that the installation does not include ODI Studio. However, if you have
ODI Studio installed, you can perform equivalent steps within ODI Studio.
To use Oracle Data Integrator from a command line:
1. Launch a Shell (UNIX), a Command Prompt (Windows) or a QSH session (AS/400).
2. Go to the …/oracledi/agent/bin or ...\oracledi\agent\bin sub-directory of the Oracle Data Integrator

installation directory.
3. Launch the startcmd.bat (on Windows) or startcmd.sh (on UNIX and AS/400) command, with the following
syntax: startcmd <command_name> [<command_parameters>]*
Importing ODI objects using a command line:
Use the following command to import the contents of an XML export file to a repository. This command
reproduces the behavior of the import feature that is available from the user interface. The object is
imported into the connected master or work repository or into the <workRepositoryName> work repository
attached to the connected master repository.
OdiImportObject FILE_NAME=<FileName> [
WORK_REP_NAME=<workRepositoryName>] [IMPORT_MODE=<DUPLICATION |
SYNONYM_INSERT | SYNONYM_UPDATE | SYNONYM_INSERT_UPDATE>]
To import the ODI artifacts into the defined work repository, you must copy two xml files from the assigned
disk into the c:\temp (for Windows) or /tmp (for Linux):
 For model folder: MFOL_Fusion_Accounting_Hub.xml
 For project: PROJ_FSCM_GL_PSGLJournalTransfer.xml

22B Importing the Model Folder Using Command Lines
Use the following commands to import the Model Folder, Fusion Accounting Hub, and two models defined
as Oracle Fusion General Ledger and Oracle PeopleSoft General Ledger.
To Import the Model Folder Using Windows:
Move to \Oracle\Middleware\Oracle_ODI1\Oracledi\agent\bin folder,
Startcmd OdiImportObject FILE_NAME=c:\temp\ MFOL_Fusion_Accounting_Hub.xml
WORK_REP_NAME=<workRepositoryName>] IMPORT_MODE=SYNONYM_INSERT
To Import the Model Folder Using Linux:
Move to /../odi/Oracledi/agent/bin folder,
Startcmd OdiImportObject FILE_NAME=/tmp/MFOL_Fusion_Accounting_Hub.xml
Where WORK_REP_NAME=<workRepositoryName> Ł Name of the work repository into which the
object must be imported. This work repository must be defined in the connected master repository. If this
parameter is not specified, then the object is imported into the current master or work repository.
For example, WORK_REP_NAME=WORK_REP where WORK_REP is the name of work repository.
Note: You must use the WORK_REP_NAME that was created during the ODI install and repository
creation.
For a listing of ODI Artifacts that are included in the Model Folder to be imported, see Appendix A:. ODI 112H
Model Folder Artifacts for PeopleSoft General Ledger to Fusion Accounting Hub Integration.

23B Importing the Project Using Command Lines

Use the following commands to import the Project, FSCM_GL_PSGLJournalTransfer, along with the
artifacts: project folder, packages, interfaces, procedures, variables, sequences, user functions and
Knowledge modules.
To Import the Project Using Windows:

Move to \Oracle\Middleware\Oracle_ODI1\Oracledi\agent\bin folder,
Startcmd OdiImportObject
FILE_NAME=c:\temp\PROJ_FSCM_GL_PSGLJournalTransfer.xml
To Import the Project Using Linux:

Move to /../odi/Oracledi/agent/bin folder,
Startcmd OdiImportObject
FILE_NAME=/tmp/PROJ_FSCM_GL_PSGL_JournalTransfer.xml
Where WORK_REP_NAME=<workRepositoryName> Ł Name of the work repository into which the
object must be imported. This work repository must be defined in the connected master repository. If this
parameter is not specified, then the object is imported into the current master or work repository.
For example, WORK_REP_NAME=WORK_REP where WORK_REP is the name of work repository.
Note: You must use the WORK_REP_NAME that was created during the ODI install and repository
creation.
For a listing of ODI Artifacts that are included in the Project to be imported, see Appendix B: ODI Project
113H
Artifacts for PeopleSoft General Ledger to Fusion Accounting Hub Integration.

37B Update the Schema and Work Schema Names in the Data Server
Setup
Update the Schema and Work Schema names left blank in the first step, Create Data Servers for Source
114H
and Target Databases through the Oracle Data Integrator Console.
1. Configure the Physical Schema for Peoplesoft (Source Database) for Data Server,
ORACLE_PEOPLESOFT_FAH:
Schema name = <PeopleSoft schema>
Work Schema name = <PeopleSoft schema>
Enter the schema name used in your PeopleSoft database; typically, the same schema is used for both.
2. Configure the Physical Schema for Fusion (Target Database) for Data Server, ORACLE_FUSION_FAH:
Schema name = FUSION
Work Schema name = FUSION_ODI_STAGE
The ODI process during execution creates temporary tables, grant privileges to create, insert, update,
delete and drop the following tables in the FUSION_ODI_STAGE (work) schema:
C$_0VS_VALUES_B_KEY
VS_VALUES_B_KEY
C$_0FND_VS_VALUES_B
I$_FND_VS_VALUES_B (Indexes: I$_FND_VS_VALUES_B_IDX, FND_VS_VALUES_B_U1_flow and
FND_VS_VALUES_B_U2_flow)
SNP_CHECK_TAB
E$_FND_VS_VALUES_B (Index: E$_FND_VS_VALUES_B_IDX)
C$_0FND_VS_VALUES_TL
I$_FND_VS_VALUES_TL (Index: I$_FND_VS_VALUES_TL_IDX)
E$_FND_VS_VALUES_TL (Index: E$_FND_VS_VALUES_TL_IDX)
C$_0GL_XFR_PSFT_RAW_INT
I$_GL_XFR_PSFT_RAW_INT

Launching the GL_SET_FUSION_USER scenario

This scenario sets the Fusion User ID that is used in the GL Journal Transfer ODI (Scenario:
GL_JOURNAL_TRANSFER) to initiate the import process in Fusion after transferring the GL Journals into
the Fusion interface table.
1. Launch a Shell (UNIX), a Command Prompt (Windows) or a QSH session (AS/400).

2. Go to the /oracledi/agent/bin or..\oracledi\agent\bin sub-directory of the Oracle Data Integrator
installation directory.
3. (For Windows) Launch the startscen.bat command, with the following syntax:
startscen.bat GL_SET_FUSION_USER 001 DEVELOPMENT_FAH "NAME=<localagent>"
"FSCM_GL_PSGLJOURNALTRANSFER.V_FUSION_USER=<userid>"
4. (For UNIX and AS/400) Launch the startscen.sh command, with the following syntax:
./startscen.sh GL_SET_FUSION_USER 001 DEVELOPMENT_FAH NAME=<localagent>
FSCM_GL_PSGLJOURNALTRANSFER.V_FUSION_USER=<userid>
Note: Replace <localagent> with the agent name used in the ODI setup and <userid> with the User ID for
the Fusion application.

Chapter 4
Setting Up PeopleSoft General Ledger for the Fusion
Accounting Hub Integration
This chapter discusses the following implementation steps within PeopleSoft General Ledger:
115H Updating Permission List for Access.
116H Mapping PeopleSoft System ID and Transfer ID.
117H Mapping Source to Target Language.
118H Mapping PeopleSoft and Fusion Account Types.
119H Mapping PeopleSoft ChartFields to Fusion Segments.
120H Mapping SetID and ChartField Combinations to Fusion Value Set Codes.
121H Mapping PeopleSoft Ledgers to Fusion Ledgers.
122H Mapping Adjustment and Closing Periods.
123H Transforming PeopleSoft Journals to Fusion Journals.
124H Drilling Back from Fusion Accounting Hub Journals to PeopleSoft Journals.
125H (return to checklist)

Updating Permission List for Access 126H (return to checklist)
To update the appropriate permission list for access to the Fusion Accounting Hub components:
Access the Permission Lists - Pages page for the permission list of those for whom you are granting
access (PeopleTools, Security, Permissions & Roles, Permission Lists):
1. Click the Find link and enter PROCESS_JOURNALS (then click OK) to edit those components for
access.
2. Select the Edit Components link of the PROCESS_JOURNALS menu name and set appropriate
permissions for each of the FUS_ components:
For more information, see PeopleTools Security Administration, Setting Up Permission Lists, Defining
Permissions.

30B Mapping PeopleSoft System ID and Transfer ID 127H (return to checklist)
Access the Setup Options page (General Ledger, Fusion Accounting Hub, Setup Options):
The values on the Setup Options page populate their respective fields in the integration table (PeopleSoft
record FUS_GL_XFER_INTF.) (ODI transfers data from this record to the Fusion integration record,
GL_XFR_PSFT_RAW_INT).
PeopleSoft Enter the PeopleSoft system identifier. This number is registered in Fusion Accounting
System ID Hub (FAH) and relates to a unique PeopleSoft instance. This way, if there are multiple
PeopleSoft instances, each one has its own System ID that is registered in FAH so
that Fusion can identify from which PeopleSoft instance that a journal originates. See
Registering Apps Unlimited Instances.
128H
Transfer ID This is a system-generated value and is automatically incremented and assigned for
each journal transformation process or initial ledger balance transformation process.
24B Mapping Source to Target Language

The language mapping is used when generating the Value Set values from the Value Set Mapping page
to map the ChartField value descriptions for a specific language to its corresponding language in Fusion.
Although you may not be transferring multiple language descriptions from PeopleSoft, you must set up
the language mapping if the Fusion database is set up for multiple languages to avoid processing errors.
Access the Language Mapping page (General Ledger, Fusion Accounting Hub, Language Mapping):
Source Select the language

Language
Target Language Enter the correspond
transformed journals
Target Base Enter the correspond

Language the transformed journ

1B Mapping PeopleSoft and Fusion Account Types 129H (return to checklist)
Access the Account Type Mapping page (General Ledger, Fusion Accounting Hub, Account Type
Mapping, Account Type Mapping):
Use the Account Type Mapping page to map the PeopleSoft Account Types by setID to the Fusion
Account Types. Keep the following in mind as you enter the values for this page:
 This mapping is used when generating Value Set values on the Value Set Mapping page.
 You must map all PeopleSoft Account Types that exist in the Account ChartField table as well as
those mapped in the Value Set mapping. Upon saving the page, you will receive an error if there are
any values that are missing.
 You can have a many (PeopleSoft) to one (Fusion) mapping as the PeopleSoft Account Type is
qualified by setID.
See also Verifying Fusion Account Types.
130H

28B Mapping PeopleSoft ChartFields to Fusion Segments 131H (return to checklist)
Access the ChartField / Segment Mapping page (General Ledger, Fusion Accounting Hub, ChartField /
Segment Mapping, ChartField / Segment Mapping):
Use the ChartField / Segment Mapping page to map all PeopleSoft ChartFields to Fusion segments.
ChartField Map the active PeopleSoft ChartFields to their corresponding Fusion Segment. This
includes GL Business Unit, and Book Code (if enabled). As is the case on the Value
Set Mapping page, map the Project ID but not the other Project Costing ChartFields
(such as PC Business Unit, Activity ID, Resource Type, or Analysis Type.) This page
requires a one-to-one mapping relationship.
Upon saving, an error message appears if an active ChartField is not mapped or if
there is a many-to-one or one-to-many mapping relationship.
You cannot map the Affiliate fields as there are no corresponding Fusion segments.
Fusion Column Select the Fusion segment counterpart for each PeopleSoft ChartField. This mapping
Name is used by the PS GL journal transform/staging process to populate the transfer
staging table, which stores segments rather than ChartFields.
Pre-Load Click this button to pre-load the PeopleSoft ChartFields on the page (rather than
ChartFields manually entering or selecting them). Then, assign the segment number for each
ChartField that is loaded. You can click the Customize link to sort by Segment after
assigning the mapping, or sort by Peoplesoft ChartField, to verify your work. After
initial data loading through the transformation process (data maintained in
FUS_CFSEGM_MTBL), you can use the Pre-Load button to ensure that your mapping
includes all currently active ChartFields.

29B Mapping SetID and ChartField Combinations to Fusion Value Set

Codes (return to checklist) 132H
Access the Value Set Mapping page (General Ledger, Fusion Accounting Hub, Value Set Mapping, Value
Set Mapping):
Use the Value Set Mapping page to map each PeopleSoft ChartField and setID combination to its
7B
corresponding Fusion Value Set Code. Once you have entered all data, click the Run button to populate
the Value Set staging table.
Note: You must complete the ChartField / Segment Mapping page first before beginning the Value Set
133H
Mapping. This provides the prompting values for the page.
The following table presents an example of the data that is stored when completing the Value Set
Mapping page:
PeopleSoft setID PeopleSoft Fusion Value Set Code

ChartField
- BUSINESS_UNIT US01_COMPANY
SHARE ACCOUNT US_ACCOUNT
JPN01 ACCOUNT JAPANESE_ACCOUNT
FRA01 DEPTID EUROPEAN_DEPARTMENT
SHARE DEPTID US_DEPARTMENT

25B Keep the following in mind when completing the Value Set Mapping page:
 Each combination of setID and ChartField that has associated recorded data should have a mapping
row on this page.
 Enter the Fusion Value Set Code manually and precisely as it appears in Fusion (case-sensitive).
 This mapping is used for the initial publish (load) of PeopleSoft ChartField values to Fusion Value
Sets.
Note: Only a one-time Value Set load is supported per PeopleSoft instance.
 Although Business Unit is not considered a ChartField, it must be mapped to its corresponding Fusion
Value Set. SetID should be blank as business units have no associated setID.
 Each Fusion Value Set code row must be unique. In other words, there should not be a many
(PeopleSoft) to one (Fusion) mapping on this page.
 Affiliate and Affiliate_Intra ChartFields are excluded from this mapping.
 If a certain ChartField and setID combination is omitted, existing ChartField values for that setID will
not be published to Fusion.
 Project ID is mapped as all the other ChartFields; however, other Project Costing ChartFields should
be excluded (Activity ID, Resource Type, Resource Category, Resource Subcategory, Analysis Type,
and PC Business Unit).
 When ready to initially load and build the Value Set staging table, click the Run button to launch the
FUS_CFANLYZR Application Engine process (make sure you have completed the Account Type 134H
Mapping page and the Language Mapping page before launching the process). This process
135H
provides an error message when duplicate rows exist.
 When the process is complete, check the process monitor. Then, log into Fusion and verify that the
Value Sets transferred successfully.
See Setting Up Fusion, Defining Target Value Sets for Corresponding PeopleSoft ChartFields.
136H

26B Mapping PeopleSoft Ledgers to Fusion Ledgers 137H (return to checklist)
Access the Ledger Mapping page (General Ledger, Fusion Accounting Hub, Ledger Mapping, Ledger
Mapping):
The ledger mapping is used during journal transformation to validate the data between the PeopleSoft
and Fusion databases. Use the Ledger Mapping page to map each combination of PeopleSoft GL
Business Unit and PeopleSoft Ledger to a Fusion ledger
Business Unit Select the PeopleSoft business unit of the ledger that you are mapping to a Fusion
ledger.
Ledger Select the PeopleSoft ledger that you are mapping to a Fusion ledger.
Note: If a GL business unit and ledger combination is omitted from this mapping, the journals from that
business unit and ledger combination will not be transferred to Fusion General Ledger.
Fusion Ledger Enter the name of the Fusion ledger to which you want to transfer the journals of the
Name specified PeopleSoft business unit and ledger combination.
Fusion COA Enter the Fusion COA (chart of accounts) Mapping Name if the Fusion ledger to which
Mapping Name you are transferring PeopleSoft journals has different chart of accounts values than
the ChartField values. Otherwise, you can leave this field blank.
Note: The Fusion Ledger Name and Fusion COA Mapping name field values are entered as free-form
text and maintained manually; as such, be sure to enter the values exactly as they appear in the Fusion
application (case-sensitive). If these field values are invalid, the PeopleSoft Import and Transform
program reports an error.
Ledger Map Details for Fusion

The Transfer ID, Status Code, Fiscal Year, and Last Update Timestamp fields are populated by the
PeopleSoft GL Journal Transform and Staging process (FUS_PSJRNLTR Application Engine program):

Transfer ID Once the PeopleSoft GL Journal Transform and Staging process is run, this field is
populated with the Transfer IDs of the processes that you have run. This value is a
system-generated counter and is automatically incremented and assigned for each
journal transformation, or initial ledger balance transformation, process.
Status Code Displays the status of each PeopleSoft GL Journal Transform and Staging process
that has been run. Values are:
 TRANSFERRED
 READY TO TRANSFER
 ERROR
Fiscal Year Displays the fiscal year in which the PeopleSoft GL Journal Transform and Staging
process was initiated.
Last Update Displays the date and time for which the process was last run.
Timestamp
The following table represents an example of the stored data from the ledger mapping:
PeopleSoft PeopleSoft Fusion Fusion Fiscal Transfer Last Status

GL Ledger Ledger Name COA Year ID Update Code
Business Mapping Timestamp
Unit Name
US001 LOCAL PeopleSoft 2011 1 07/29/11 Transferred

Local USD 12:38AM
US002 CORPORATE PeopleSoft PeopleSoft 2011 1 07/29/11 Transferred

Corporate 12:38AM
FRA01 EURO PeopleSoft 2011 2 07/31/11 Ready to

France EUR 4:01AM Transfer
FRA01 CORPORATE PeopleSoft PeopleSoft 2011 2 07/31/11 Ready to

France EUR 4:01AM Transfer
Note: You can map multiple PeopleSoft GL business unit and ledger combinations to the same Fusion
ledger, provided they have the same base currency (ledger currency or inherited business unit base
currency). There is no currency validation on this page; it is advisable to manually validate your data.
Note: Although you can map multiple PeopleSoft GL business unit and ledger combinations to one
Fusion ledger, you cannot map one PeopleSoft GL business unit and ledger combination to many Fusion
ledgers.
See Setting Up Fusion, Entering Target Ledgers in Fusion General Ledger.

138H

27B Mapping Adjustment and Closing Periods 139H (return to checklist)
Access the Adjustment/Closing Period Mapping page (General Ledger, Fusion Accounting Hub,
Adjustment/Closing Period Mapping, Adjustment/Closing Period Mapping):
The Adjustment/Closing Period Mapping is used during journal transformation to relate PeopleSoft GL
adjustment and closing journals to their corresponding Fusion period. During journal transformation, the
Peoplesoft journal data is validated by Open Calendar / Adjustment Period with setID and Calendar ID
and transferred to the Fusion interface staging table within Peoplesoft (FUS_GL_XFR_INTF).
The following table presents an example of the stored data in FUS_CALADJ_MTBL:
PeopleSoft PeopleSoft PeopleSoft PeopleSoft Fusion Period

SetID Calendar Fiscal Year Adjustment Name
Period
SHARE 01 2011 901 AD32011-01
SHARE 01 2011 902 AD32011-02

... ... ... ... ...
SHARE 01 2011 912 AD32011-12
SHARE 01 2011 999 CLOSE2011
SHARE 01 2012 901 AD32012-01
Keep the following in mind as you enter data for this page:

 This mapping is used by the PeopleSoft GL Journal transform/staging process when the journal
header indicates that it is an adjusting entry or a year-end closing entry.
 The corresponding Fusion period name can be an adjustment or a regular period.
 PeopleSoft journals that are booked in regular accounting periods are not processed through this
mapping. They are automatically posted to the Fusion period that corresponds to the PeopleSoft
journal date.
 You can map many PeopleSoft periods to one Fusion period.
 The Fusion Period Name field is a free form text field. Enter the name exactly as it appears in the
Fusion application (case-sensitive).
See Setting Up Fusion, Setting Up Calendars and Opening Accounting Periods for the Ledgers.
140H

36B Transforming PeopleSoft Journals to Fusion Journals 141H (return to checklist)
Access the Transform/Stage GL Journals page (General Ledger, Fusion Accounting Hub,
Transform/Stage GL Journals, Transform/Stage GL Journals):
This process request launches the Transform/Stage GL Journals process (FUS_PSJRNLTR Application
Engine program), which transforms the PeopleSoft GL posted journals based upon the data mapping
tables and stages the new Fusion journal data in the integration table (GL_XFR_PSFT_RAW_INT).
Request Number You can create one or multiple requests to process at once. Click the plus button to
create additional requests to be processed.
Business Unit Select to process the request for a specific business unit. You can create multiple
requests if you want to run the process for more than one business unit. This field is
required when processing regular journal transfers (you can leave the field blank for
initial load or retransfer to process all business units).
Ledger Select to process the request for a specific ledger. You can create multiple requests if
you want to run the process for more than one ledger. This field is required when
processing regular journal transfers (you can leave the field blank for initial load or
retransfer if you want to process all ledgers meeting other criteria).
Load Initial Balance Entry
Fiscal Year Enter the fiscal year for which you want to load initial balances. This determines the
earliest journal data to be transferred to Fusion.
Load Initial Select this option to load your initial balances at implementation time, for example. If
Balances you select this option, you must specify a Business Unit, Ledger, and Fiscal Year. All
other options cannot be selected. Beginning balances for the selected fiscal year are
retrieved from the ending balances of the previous year from the PS_LEDGER table.
Cut Off Date Enter a date that represents the last journal date in the date selection range for which

to process journals for transfer to Fusion. If you leave this field blank, then all posted
journals that have not yet been processed by the transfer program and that meet the
selected criteria will be processed by the request for transfer.
Reprocess / Retransfer Process
Transfer ID Select the Transfer ID of the instance that you would like to reprocess. The values that
appear are those for which the process had previously been launched but had ended in
error or if for some reason Fusion was unable to process the batch. Once you have
corrected any errors or want to reinitiate the process, you can reprocess the batch. If it
is transferred successfully, the Transfer ID will no longer be available in the prompt list
for reprocessing.
Reprocess / Select this check box to reprocess and retransfer the selected Transfer ID to Fusion
ReTransfer General Ledger.
Process
1. Once you have loaded the initial balances or process a transfer, reconcile the resulting balances
within Fusion to the original transferred balances in PeopleSoft. Note that the Drillback feature
from Fusion to PeopleSoft journals is not supported for initial balances.
2. When the process is complete, the Fusion Journal Import process should launch within the
Fusion database. Verify the accuracy of the Import and Transform report in Fusion (Transfer ID,
total number of lines).
See Setting Up Fusion, Initiate Transactions from PeopleSoft and Verify Results.
142H
3. Review and resolve any exceptions that are raised from within Fusion. An error is sent to the
PeopleSoft database with exceptions regarding inconsistencies in control data matching.
4. To facilitate your reconciliation process, you can also run respective trial balances in each system
(or use any number of reporting options, such as PS/nVision or PS/Query.

8B Drilling Back from Fusion Accounting Hub Journals to PeopleSoft

Journals
Once you have transferred your PeopleSoft journals to Fusion, you can log in to the Fusion Accounting
Hub application and, from an inquiry page, review your journals and drill back to the original PeopleSoft
journal details.
Make sure you have performed the necessary setup steps within Fusion Accounting Hub to enable user
drillback to PeopleSoft General Ledger. For details, see Registering Apps Unlimited Instances.
144H
You can also directly access the Journal Line drill back page from PeopleSoft to view the transferred
journals and drill down to the original journal details (General Ledger, Fusion Accounting Hub, Journal
Line):
Click the GL Journal link from the Journal Line drill back page to access the Review Journal Status -
Journal Lines page for details and status of the original journal entry:
Click the Journal Header page to review the journal header details and status:

PeopleSoft delivers a URL that allows drillback from the Fusion journal inquiry application page to the
PeopleSoft Journal Line drill back page. There is no setup for enabling the URL for drillback within
PeopleSoft. The setup takes place within Fusion.
See Registering Apps Unlimited Instances.
145H
Note: Drillback from Fusion to PeopleSoft is not supported for initial balances that are loaded to
19B18B16B 15B11B 10B9B
Fusion.

Chapter 5
Configuring Fusion for the PeopleSoft GL to Fusion
Before you process the integration between PeopleSoft GL and Fusion Accounting Hub, you must
manually configure Fusion General Ledger to reflect the structure that is necessary to process the
PeopleSoft journals according to your mapping considerations and resulting structure. Following are the
setup steps for the Fusion Accounting Hub that are needed for this integration:
147H Overview of Fusion Accounting Hub delivered objects.
148H Performing Post-Installation Steps.
149H Registering Apps Unlimited Instances.
150H Verifying Fusion Account Types.
151H Defining Target Value Sets for Corresponding PeopleSoft ChartFields.
152H Defining the Accounting Flexfield (Chart of Accounts)
153H Flexfield Qualifiers
154H Enable Dynamic Inserts
155H Freeze and Compile Accounting Structure
156H Open Accounting Periods for the Ledgers
157H Creating Target Ledgers in Fusion General Ledger.
158H Initiating Transaction Processing and Verifying Results.
159H Reviewing the Fusion Journals and Drilling Back to PeopleSoft Source Journals
For documentation of Fusion Accounting Hub implementation detail, consult the following resources:
160H Oracle® Fusion Accounting Hub Implementation Guide
161H Oracle® Fusion Applications Administrator and Implementor Roadmap
162H Oracle® Fusion Applications Financials Implementation Guide
163H Oracle® Fusion Applications Common Implementation Guide

Overview of the Fusion Accounting Hub Delivered Objects for the Integration
Once installed, Fusion Accounting Hub includes the following objects that are unique to the PeopleSoft
GL integration:
A new table, GL_XFR_PSFT_RAW_INT, which is populated by the Transform/Stage GL Journals
process that is launched within PeopleSoft (FUS_PSJRNLTR Application Engine program). This
164H
process transforms the PeopleSoft GL posted journals based upon the PeopleSoft data mapping
tables and stages the data within Fusion Accounting Hub, extending the relevant transformed data
necessary for creating Fusion journals.
Application interfaces include:
Fusion Program Name Description

Imports and transforms PeopleSoft staged journal
lines into Fusion General Ledger journal lines that
PeopleSoft Import and Transform program are stored in the GL_XFR_PSFT_INTERFACE table
until the Journal Import process creates the Fusion
journal entries.
Presented below are the key Fusion tables that are used:
Fusion Table Description
Staging table within Fusion database. ODI transfers

GL_XFR_PSFT_RAW_INT the journal lines from the PeopleSoft staging record
(FUS_GL_XFR_INTF) to this table in Fusion (see
first bullet point above).
Table within Fusion database that contains the

transformed data produced by the PeopleSoft Import
GL_XFR_PSFT_INTERFACE
and Transform program until Journal Import process
creates journals from it
GL_JE_HEADERS Stores the Fusion accounting header information.
GL_JE_LINES Stores the Fusion accounting line detail information.
GL_CODE_COMBINATIONS Stores the chart of accounts segment details.
GL_LEDGERS Stores the ledger level details.

35B12B Registering Apps Unlimited Instances 165H (return to checklist)
Once signed into Fusion Accounting Hub:

1. From the Navigator menu, select the Setup and Maintenance link. (You may need to click the More
link to view all of the menus. Setup and Maintenance may be found within the Tools menu.)
2. Navigate to the All Tasks tab and enter Register Applications Coexistence Instances for PeopleSoft in
the Name field.
3. Click the Search button.
4. From the results grid, click the Go to Task icon.
 Verify that the data is entered in the mandatory fields:
o Application Type = PeopleSoft
o System Identifier - this number should be the System ID that is used in PeopleSoft
(see Mapping PeopleSoft System ID and Transfer ID)
166H
o Name (Instance)
o Journal Source
 Verify that the Ledger Assignments button is inactive when PeopleSoft is selected for the
Application Type.
 Verify that the (Drilldown) URL is entered and is in the correct format. This enables drillback from
38B
Fusion Accounting Hub to the originating PeopleSoft journal.
The URL syntax for the non-dynamic portion is as follows:

http://server/servlet_name/SiteName/PortalName/NodeName/c/PROCESS_JOURNALS.FUS_DRILLBACK_JRNL.GBL
The following table describes the elements within the URL format above:
URL Element Description
http://server/ Scheme (http or https) and the web server name
servlet_name/ Name of the physical servlet that the web server invokes to handle the request
SiteName/ Site name specified during Oracle PeopleSoft Pure Internet Architecture setup
PortalName/ Name of the portal to use for this request
NodeName Name of the node that contains the content for this request
See Drilling Back from Fusion Accounting Hub Journals to PeopleSoft Journals.
167H

Verifying Fusion Account Types

Account Types represent basic attributes that control the accounting behavior of the values and
combinations. The account types are delivered with the database when Fusion Accounting Hub is
installed. Make sure that your mapping in PeopleSoft is accurate.
Verify the Account Type mapping in PeopleSoft is accurate. See Mapping PeopleSoft and Fusion Account Types.
168H
PSFT Description Fusion

A Assets A
E Expense E
L Liabilities L
Q Equity O
R Revenue R
Oracle® Fusion Applications Common Implementation Guide, Define Enterprise Structures, Define Chart
169H
of Accounts for Enterprise Structures: Manage Chart of Accounts Value Sets.
Defining Target Value Sets for Corresponding PeopleSoft ChartFields

Value Sets are the Fusion equivalent to the PeopleSoft combination of setID and ChartField.
Value Sets are the containers that hold the set of reusable values that are tied to corresponding chart of
accounts (COA) segments. Together, the values for all the COA segments form a meaningful
combination. The values and the combinations are driven by a set of attributes (account types) that
control the accounting behavior.
The initial load of Value Sets is launched from the PeopleSoft Application Engine process
(FUS_CFANLYZR). This is a one-time transfer per PeopleSoft instance. For ongoing updates, you must
manually maintain the Value Sets within Fusion and coordinate with PeopleSoft updates.
Oracle® Fusion Applications Common Implementation Guide, Define Enterprise Structures, Define Chart
171H
of Accounts for Enterprise Structures: Manage Chart of Accounts Value Sets.
See Setting up PeopleSoft, Mapping SetID and ChartField Combinations to Fusion Value Set Codes.
172H

Defining the Accounting Flexfield (Chart of Accounts)

The chart of accounts defines the number and attributes of various segments, including the order of
segments, the width of segments, prompts, and segment labels, such as balancing, natural account, and
cost center. The chart of accounts further defines the combination of value sets associated with each
segment of the chart of accounts, as well as the type, default value, additional conditions designating the
source of the values using database tables, and the required and displayed properties for the segments.
Define the Chart of Accounts that corresponds to the PeopleSoft ChartFields.
.1 Add the Chart of Accounts in Fusion to correspond to the PeopleSoft ChartFields. You must manually maintain
these on an ongoing basis.
.2 From the Navigator menu, select the Setup and Maintenance link. (You may need to click the More link to view
all of the menus. Setup and Maintenance may be found within the Tools menu.)
.3 Navigate to the All Tasks tab and enter Define Chart of Accounts for Enterprise Structures in the Name field.
.4 Click the Search button and click the Create button to:
.a Define Segments
.b Identify Balancing and Natural Account Segments through Segment Labels
.c Enable Dynamic Insertion (optional)
.d Deploy the Accounting Structure
See Setting up PeopleSoft, Mapping PeopleSoft ChartFields to Fusion Segments.
174H
See Oracle® Fusion Applications Common Implementation Guide, Define Enterprise Structures, Define
175H
Chart of Accounts for Enterprise Structures: Manage Chart of Accounts.
Identifying Balancing and Natural Account Segments through Segment Labels

Segment Labels (or Flexfield Qualifiers) are the set of attributes that add functionality to each segment.
For example, the Balancing Segment qualifier represents a balancing segment that ensures the debit and
credit balancing at this segment level. The Account Segment qualifier is used to enable the account type
attributes.
176H
Chart of Accounts for Enterprise Structures: Manage Chart of Accounts, Segment Labels.
Enable Dynamic Insertion

Dynamic inserts are required to create account code combinations on the fly. Enable dynamic inserts by
selecting the Allow Dynamic Inserts check box on the Flexfield Segments page.
Deploy the Accounting Structure

Once you have created the accounting flexfield, you must deploy it. Once it has deployed successfully,
restart the application servers.
177H
Chart of Accounts for Enterprise Structures: Manage Chart of Accounts.

Setting Up Calendars and Opening Accounting Periods for the

Ledgers
You will need to create the calendars in Fusion Accounting Hub to match those in PeopleSoft and make
sure the appropriate periods are open for posting. The ledger activity for a calendar period is controlled at
the ledger level in Fusion Accounting Hub.
Complete the following setup for accounting periods:
.1 Once signed into FAH, from the General Accounting Dashboard, select Manage Accounting Calendars.
.2 Add a new value.
.3 Manually define the Period types and the periods prior to setting up the calendar to match with the GL periods of
PeopleSoft.
.4 Manually set up the calendar with appropriate accounting periods. The calendars defined and assigned to a
Fusion ledger must match the calendar definition assigned to the corresponding PeopleSoft business unit and
ledger. The following attributes of the calendar should be the same:
.a Number of (non-adjustment) accounting periods
.b Year start date and end date
.c Start and end dates of accounting periods
.d Verify that the Fusion journal date is the end of period date for the mapped Fusion period.
.5 Manually synchronize the period statuses with those within PeopleSoft.

.6 Coordinate the source to target mapping of adjustment and closing periods in PeopleSoft to be sure the names
are entered exactly as they appear in Fusion.
See Setting up PeopleSoft, Mapping Adjustment and Closing Periods.

179H
See Oracle® Fusion Accounting Hub Implementation Guide, Define Financial Reporting Structures,
180H
Define Calendars.
181H
Chart of Accounts for Enterprise Structures: Manage Accounting Calendars.

Creating Target Ledgers in Fusion Accounting Hub

Manually set up the primary ledgers reflecting the PeopleSoft ledger and business unit combination
mapping.
See Setting up PeopleSoft, Mapping PeopleSoft Ledgers to Fusion Ledgers.
183H
To create the Fusion ledgers in Fusion Accounting Hub:
.1 From the Navigator menu, select the Setup and Maintenance link. (You may need to click the More link to view
all of the menus. Setup and Maintenance may be found within the Tools menu.)
.2 Navigate to the All Tasks tab and enter Define Accounting Configurations for Enterprise Structures in the Name
field.
.3 Click the Go To Task button for the Manage Primary Ledger task and click the Create button.
.4 Specify the fiscal calendar, currency to be used (same as PeopleSoft ledger), journal processing methods and
accounting options.
.5 Optionally associate the Legal Entity with the Ledger.
.6 Define Accounting and Ledger Options like Ledger Short Name, retained earnings account and optionally
Journal Processing and Journal Reconciliation options.
.7 Assign the balancing segment value to each ledger:
.8 Optionally specify the Reporting Currency as per the business requirement.
.9 Define Ledger Accounting Methods.
.10 Complete Accounting Setup: Click the Review and Submit Accounting Configuration link.
.11 This process generates Data Access Sets.
.12 Update or verify the source business unit.
See Oracle® Fusion Accounting Hub Implementation Guide, Define Ledgers.

184H

Initiating Transaction Processing and Verifying Results

After the Transform/Stage GL Journals process (FUS_PSJRNLTR Application Engine program) is

submitted from PeopleSoft (source system) to transfer journal entries to Fusion, the PeopleSoft Import and
Transform program is automatically launched. However, if for some reason you need to resubmit it, you can
do so as follows:
.1 To submit the Import and Transform program, log in to Fusion Accounting Hub:
 From the navigator, go to Scheduled Processes.
 Press the Schedule New Process button (middle of the window).
 Select the PeoplesoftTransform process name (use the Search button to retrieve) and click OK.
 Enter the Peoplesoft system name and transfer id of the data that you want to import. Only those
transfer ids that are associated with data currently in the GL_XFR_PSFT_RAW_INT staging table
are available for selection.
On an ongoing basis, verify that the PeopleSoft Import and Transform program has processed successfully
and submit journal batch for posting.
.1 Log in to Fusion Accounting Hub.

.2 To check status of processes and view the Fusion execution report, access the following:
.a From the Navigator, go to Scheduled Processes.
.b Click Search.
.c Scroll to the process that you are interested in reviewing. Make sure to click the desired process
so that it is the highlighted row. You can see the log file by pressing the view log button. You can
see the output file by scrolling to the bottom of the screen and clicking the link in the output
section.
Note: If the output file is displayed as a single line, save it to disk and then open it using WordPad.
.d Due to security, your concurrent request may not be displayed. If that is the case, contact your
Fusion system administrator to view the status, log file, and output file.
.3 Verify the accuracy of the Import and Transform report in Fusion (check Transfer ID and total number of lines).
See Oracle® Fusion Accounting Hub Implementation Guide.

186H
See also, Setting Up PeopleSoft, Transforming PeopleSoft Journals to Fusion Journals.

187H

Reviewing the Fusion Journals and Drilling Back to PeopleSoft

Source Journals
1. Review the journals. From the Navigator menu, go to the Journals workbench.
2. Check the Data Access Set (upper left of the window). Make sure it shows the ledger that you want to
access. If not, click the Change link and select the desired ledger.
3. Click Manage Journals and enter search criteria in the Search window.
4. Click on the desired journal batch for more details. You can choose to Post or Delete the batch from the
batch actions that are provided in the window
5. Select “Journals”.
6. Select the link to drill to the corresponding PeopleSoft journal.
7. The PeopleSoft Application Login browser page should launch and you are able to log in and access the
PeopleSoft journal.
See also, Drilling Back from Fusion Accounting Hub Journals to PeopleSoft Journals.
189H

Appendix A
ODI Model Folder Artifacts for PeopleSoft GL to

The following table lists the ODI Artifacts that are included in the Model Folder within the XML file,
MFOL_Fusion_Accounting_Hub.xml for import:
Model Folder : 1 Fusion Accounting Hub
Model Name : 1 Oracle Fusion General Ledger
Table Name : 1 FND_VS_VALUES_B

2 FND_VS_VALUES_TL
3 FND_VS_VALUE_SETS
4 GL_XFR_PSFT_RAW_INT
Model Name : 1 Oracle PeopleSoft General Ledger
Table Name : 1 PS_FUS_PSJRNLKEYIT

2 PS_FUS_GL_XFR_INTF
3 PS_FUS_CF_VS_VALNG
4 PS_FUS_CF_VS_VAL
5 PS_FUS_CFVS_MAP
190H Return to command line import instructions.

Appendix B
ODI Project Artifacts for PeopleSoft GL to Fusion

The following table lists the ODI Artifacts that are included in the Project within the XML file,
PROJ_FSCM_GL_PSGLJournalTransfer.xml, for import:
Project Name : 1 FSCM_GL_PSGLJournalTransfer
Project Folder Name : 1 FSCM_GL_PSGLJOURNALTRANSFER
Packages : 1 GL_COA_INITIAL_LOAD_PKG
2 GL_JOURNAL_TRANSFER
3 GL_SET_FUSION_USER
Interfaces : 1 GetJournalHdrKey_PS_FUS_PSJRNLKEYIT_Append
2 LoadFromStagingTables_GL_XFR_PSFT_RAW_INTF_Append
3 StoreKeys_FND_VS_VALUES_B
4 LoadStagingTables_FND_VS_VALUES_B_Append
5 LoadStagingTables_FND_VS_VALUES_TL_Append
Procedures : 1 DeleteFromStagingTables_PS_FUS_PSJRNLKEYIT_Delete
2 DeleteFromStagingTables_PS_FUS_PSJRNLKEYIT_By_TRANSFER_I
D_Delete
3 CommitSubmitPackage_In_Fusion_Commit
4 UpdateField_FUS_STATUS_CODE_InStagingTables_PS_FUS_GL_
XFR_INTF_Update
Variables : 1 V_CREATED_BY
2 D_CREATION_DATE
3 N_ENTERPRISE_ID
4 D_LAST_UPDATE_DATE
5 V_LAST_UPDATE_LOGIN
6 N_NEW_TRANSFERID
7 N_PSFT_SYSTEMID
8 V_FUSION_USER

User Functions
User Function's Folder 1 FusionAccountingHub
Knowledge Modules 1 ODICURRENTUSER

2 GET_MODULE_ID
Reverse-engineering (RKM) : 1 RKM Oracle

2 RKM Peoplesoft ORACLE
LOADING (LKM) : 1 LKM SQL to Oracle
Check (CKM) : 1 CKM Oracle
Integration (IKM) : 1 IKM Oracle Incremental Update

2 IKM SQL Incremental Update - FAH
3 IKM SQL Control Append
191H Return to command line import instructions.

Appendix C
PeopleSoft Journal Staging Record

The following represents columns of the new PeopleSoft Journal Staging record (FUS_GL_XFR_INTF):
PSFT Column PSFT Column Description Sample Value

PSFT System ID 2345
Transfer ID 1
Line 0 contains the status code of the journal.
Int JRNL LN Number Lines 1-….are the actual journal lines 0, 1, 2, 3…..
Unit PeopleSoft GL business unit of the journal US005
Ledger PeopleSoft Ledger CORPORATE
Fusion Ledger Fusion Ledger Name Peoplesoft QA Corporate (USD)
COA Map Name Peoplesoft QA
This is the actual PeopleSoft journal ID if journals
are transferred; or, if balances are transferred, the
Journal ID value is -1 0000000197
Status Code Appears only on Line 0 of each Transfer ID TRANSFERRED
Accounting Date PeopleSoft Journal Date 7/22/2011.
Fusion Accounting Period – this field only shows
values for adjustment periods or year-end closing
periods. Otherwise, it is blank for normal
accounting periods since the Fusion equivalent is
derived in Fusion from the PeopleSoft Accounting
Fus Acct Period Date. Adj-Q3-11
Fusion Period Fusion Period (null)
Currency Code PeopleSoft Currency Code FRF
Cur Conv Dt Currency Conversion Date 7/22/2011.
Usr Cur Conv Ty ? (null)
Cur Conv Rt Currency Conversion Rate 0.16519
SEGMENT1 PSFT Fields – Business unit

SEGMENT2 GL Account Derived from the ChartField /
SEGMENT3 (….and so on. Do not map Affiliates) Segment Mapping page
SEGMENT4
SEGMENT5
SEGMENT6
SEGMENT7
SEGMENT8
SEGMENT9
SEGMENT10
Fus PSFT CCID ? 0
Fus PSFT Combo (null)

ENTERED_DR
ENTERED_CR

Final Implementation Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Final Implementation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

PeopleSoft General Ledger 9.

Oracle Proprietary and Confidential ii

Oracle Proprietary and Confidential 1

Verifying Fusion Account Types...................................................................................................... 41

Oracle Proprietary and Confidential 2

Prerequisites and considerations.

PeopleSoft GL to Fusion Accounting Hub Integration Overview

4. PeopleSoft Component to map PeopleSoft ChartFields to Fusion Segments.

Oracle Proprietary and Confidential 3

PeopleSoft with a link to the Review Journal Status component.

Common Terminology Used in the PeopleSoft to Fusion Integration

Oracle Proprietary and Confidential 4

Prerequisites and Considerations

Ledger for the Fusion Accounting Hub Integration.

PeopleSoft GL to Fusion Accounting Hub Integration. This section includes references to

Fusion Accounting Hub operates exclusively on the Oracle database platform.

Oracle Proprietary and Confidential 5

Oracle Proprietary and Confidential 6

The implementation methodology is intended to provide a preliminary blueprint for step-by-step

Oracle Proprietary and Confidential 7

34B Overall Integration Implementation Setup and Process Flow

Oracle Proprietary and Confidential 8

33B17B13B PeopleSoft Pages Used in the Fusion Accounting Hub Integration

Page Object Name Navigation Usage

Oracle Proprietary and Confidential 9

Page Object Name Navigation Usage

Drill back from Fusion Accounting the journal details.

Records Used in the PeopleSoft to Fusion Accounting Hub Integration

Record Name Description Usage

FUS_CFSEG_MAP ChartField to Segment mapping Maps PeopleSoft ChartFields to Fusion

Oracle Proprietary and Confidential 10

32B21B20B 14B High-Level Integration Implementation Checklist

Task Task Responsible

0.1 Installation and Configuration

Oracle Proprietary and Confidential 11

 Performing post-installation steps and importing ODI artifacts

Prerequisites and Requirements 101H (return to checklist)

Web Logic Server is also used.

Performing Post-Installation Steps and Importing ODI Artifacts

3. 104H Create the context code.

4. 105H Create logical schemas for source and target databases.

5. 106H Import Model Folder using command-line instructions.

6. 107H Import Model and Project files using command-line instructions.

Oracle Proprietary and Confidential 12

Performing Post-Installation Steps 110H (return to checklist)

Field Values for PeopleSoft (Source Database) Comments

Data Server Name ORACLE_PEOPLESOFT_FAH Mandatory Value

Technology ORACLE Select platform of your PeopleSoft

Batch Update Size 30 Use default value

Array Fetch Size 30 Use default value

JDBC Driver oracle.jdbc.OracleDriver Select applicable JDBC driver for your

JDBC URL jdbc:oracle:thin:@<host>:<port>:<SID> Provide the connection information.

User and Password <UserID> Supply appropriate user ID and password

Oracle Proprietary and Confidential 13

Field Values for Fusion (Target Database) Comments

Data Server Name ORACLE_FUSION_FAH Mandatory Value

Technology ORACLE Fusion only works on Oracle platform.

Batch Update Size 30 Use default value

Array Fetch Size 30 Use default value

JDBC Driver oracle.jdbc.OracleDriver Select applicable JDBC driver for your

JDBC URL jdbc:oracle:thin:@<host>:<port>:<SID> Provide the connection information.

.4 Save each data server connection configuration.

Oracle Proprietary and Confidential 14