CLL f357 Ig US

Download as pdf or txt
Download as pdf or txt
You are on page 1of 274

LAD Add-on Localizations

Oracle Brazil
EBS-PeopleSoft HCM Integration

Implementation Guide
Release 15
December 2015
Version 15
DISCLAIMER :
CURRENTLY, ORACLE OFFERS CERTAIN RESALABLE ASSETS OR OTHER DEFINED SERVICE
DELIVERABLES (COLLECTIVELY REFERRED TO AS "SERVICE DELIVERABLES") UNDER A
LIMITED USE LICENSE. THE SERVICE DELIVERABLES CURRENTLY INCLUDE, BUT ARE NOT
LIMITED TO, ORACLE INTEGRATION HUB. YOU AGREE THAT :
(i) SERVICE DELIVERABLES ARE NOT ORACLE STANDARD SOFTWARE PROGRAMS,
(ii) TECHNICAL SUPPORT FOR SERVICE DELIVERABLES IS NOT AVAILABLE FROM OR
UNDER, OR PROVIDED BY OR THROUGH, ORACLE'S SUPPORT SERVICES
ORGANIZATION OR YOUR ORACLE PROGRAM LICENSE AGREEMENT,
(iii) YOUR RIGHT TO USE AND RECEIVE SUPPORT SERVICES FOR SERVICE DELIVERABLES
IS SOLELY AS DESCRIBED IN YOUR CONTRACT FOR SUCH SERVICE DELIVERABLES, AND
(iv) A SERVICE REQUEST REGARDING SERVICE DELIVERABLES, REGARDLESS OF HOW
INITIATED OR LOGGED, WILL BE ADDRESSED IN ACCORDANCE WITH THE TERMS OF
YOUR CONTRACT FOR SUCH SERVICE DELIVERABLES.

1.1 Document Control

Change Record

Date

Author

Version

Change Reference

12-aug-10

Arthur Costa

Creation

29-oct-10

Marcos Allonso

Review document

10-dec-10

Arthur Costa

Service Operation GP_POST_GL

11-jan-11

Marcos Allonso

Add instructions about patch 10275377

21-jan-11

Marcos Allonso

Correct Establishment Handler PeopleCode

24-feb-11

Gerson Caparelli

Add instructions about patch 11654567 (phase 2)

04-mar-11

Marcos Allonso

Add instructions about patch 11822649

23-mar-11

Arthur Costa

Add instructions about Apply PeopleSoft Package

11-apr-11

Marcos Allonso

Review instructions about Profile Definition for


BPEL Host Name

18-apr-11

Marcos Allonso

Review instructions about: BPEL Deploy Process

15-aug-11

Marcos Allonso

Add new integration point SEFIP Autonomous

12-sep-11

Marcos Allonso

Add E-Business Suite Supplier Sites extension

26-sep-11

Ricardo Cheachire

Add new integration point Accounting Reversal

04-nov-11

Marcos Allonso

Review
Setting Up: Oracle E-Business Suite Supplier Sites
Extensions

29-may-12

Marcos Allonso

Rename zip file

11-mar-13

Marcos Allonso

Review title
Add table cll_f357_references
Rename partition name ebs_psft to cll
Remove topics:
Profile Definition for BPEL Host Name
Connection Pool: OracleAppsAdapter
Service operation handler

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Document Control

ii

Date

Author

Version

Change Reference

1-may-13

Marcos Allonso

Review table cll_f357_bank_branches_polling


Add setting up establishment parameters

8-may-13

Marcos Allonso

Add new patches 16608791, 16701506, 16657397

10-jun-13

Marcos Allonso

10

Add new profiles

CLL_F357: URL for the SOA Suite for EBS-PSFT


Integration

CLL_F357: URL for the PeopleSoft Integration


Broker for EBS-PSFT Integration
12-aug-13

Marcos Allonso

11

Add new patch 17004484

13-set-13

Marcos Allonso

12

Add new column


cll_f357_gl_parameters.conversion_rate_type

17-Jun-14

Ricardo Cheachire

13

Profile name changed from Allow Extension for EBSPST Integration to Enable Extension for EBS-PST
Integration

23-Dec-14

Eduardo Leite

14

Including new objects from bugs:

Ricardo Cheachire

BUG 19510312 - ER: EBS X PEOPLE


INTEGRATION - UNBALANCED
RECORDS FOR EBS/GL;

BUG 20002148 - EBS X PEOPLE


INTEGRATION - SEND ACCOUNT /
COST CENTER TO PSFT.

BUG 18551247 - EBS X PEOPLE COST


CENTER INTEGRATION

22-Sep-15

Ricardo Cheachire

15

EBS Patch Superseded:

From 20317664 to 21762774

1.2 Send us Your Comments


Oracle welcomes customers' comments and suggestions on the quality and usefulness
of this document. Your feedback is important, and helps us to best meet your needs as
a user of our products. For example:

LAD Add-on Localizations

Are the implementation steps correct and complete?

Did you understand the context of the procedures?

EBS-PeopleSoft HCM Integration - Implementation Guide

Send us Your Comments

iii

Did you find any errors in the information?

Does the structure of the information help you with your tasks?

Do you need different information or graphics? If so, where, and in what


format?

Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell
us your name, the name of the company who has licensed our products, the title and
part number of the documentation and the chapter, section, and page number (if
available).

Note: Before sending us your comments, you might like to check that you have the
latest version of the document and if any concerns are already addressed. To do this,
access the new Applications Release Online Documentation CD available on My Oracle
Support and www.oracle.com. It contains the most current Documentation Library
plus all documents revised or released recently.
Send your comments to us using the electronic mail address: [email protected]
Please give your name, address, electronic mail address, and telephone number
(optional).
If you need assistance with Oracle software, then please contact your support
representative or Oracle Support Services.
If you require training or instruction in using Oracle software, then please contact
your Oracle local office and inquire about our Oracle University offerings. A list of
Oracle offices is available on our Web site at www.oracle.com.
1.3 Preface

1.3.1 Intended Audience


Welcome to Release 12 of the LAD Add-On Localizations: EBS-PeopleSoft HCM
Integration Implementation Guide.

This guide assumes you have a working knowledge of the following:

LAD Add-on Localizations

The principles and customary practices of your business area.

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

iv

Computer desktop application usage and terminology


If you have never used Oracle Applications, we suggest you attend one or more of the
Oracle Applications training classes available through Oracle University.

1.3.2 Deaf/Hard of Hearing Access to Oracle Support Services


To reach Oracle Support Services, use a telecommunications relay service (TRS) to call
Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle
technical issues and provide customer support according to the Oracle service request
process. Information about TRS is available at
http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is
available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

1.3.3 Documentation Accessibility


Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at http://www.oracle.com/accessibility/ .

1.3.4 Accessibility of Code Examples in Documentation


Screen readers may not always correctly read the code examples in this document.
The conventions for writing code require that closing braces should appear on an
otherwise empty line; however, some screen readers may not always read a line of
text that consists solely of a bracket or brace.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

1.3.5 Accessibility of Links to External Web Sites in Documentation


This documentation may contain links to Web sites of other companies or organizations that
Oracle does not own or control. Oracle neither evaluates nor makes any representations
regarding the accessibility of these Web sites.

1.3.6 Structure

1.3.7 Related Information Sources


This document is available through My Oracle Support.
If this guide refers you to other Oracle Applications documentation, use only the
Release 12 versions of those guides.
For a full list of documentation resources for Oracle Applications Release 12, see Oracle
Applications Documentation Resources, Release 12, My Oracle Support Document
394692.1.
Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).

PDF - PDF documentation is available for download from the Oracle


Technology Network at http://otn.oracle.com/documentation.

Online Help - Online help patches (HTML) are available on My Oracle Support.

My Oracle Support Knowledge Browser - The OracleMy Oracle Support


Knowledge Browser lets you browse the knowledge base, from a single product
page, to find all documents for that product area. Use the Knowledge Browser
to search for release-specific information, such as FAQs, recent patches, alerts,
white papers, troubleshooting tips, and other archived documents.

Oracle E-Business Suite Electronic Technical Reference Manuals - Each


Electronic Technical Reference Manual (eTRM) contains database diagrams and a
detailed description of database tables, forms, reports, and programs for a
specific Oracle Applications product. This information helps you convert data

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

vi

from your existing applications and integrate Oracle Applications data with nonOracle applications, and write custom reports for Oracle Applications products.
Oracle eTRM is available on My Oracle Support.
1.3.7.1 Related Guides

You should have the following related books on hand. Depending on the requirements
of your particular installation, you may also need additional manuals or guides.
Oracle Applications Installation Guide: Using Rapid Install:
This book is intended for use by anyone who is responsible for installing or upgrading
Oracle Applications. It provides instructions for running Rapid Install either to carry out
a fresh installation of Oracle Applications Release 12, or as part of an upgrade from
Release 11i to Release 12. The book also describes the steps needed to install the
technology stack components only, for the special situations where this is applicable.
Oracle Applications System Administrator's Guide Documentation Set
This documentation set provides planning and reference information for the Oracle
Applications System Administrator. Oracle Applications System Administrator's Guide Configuration contains information on system configuration steps, including defining
concurrent programs and managers, enabling Oracle Applications Manager features,
and setting up printers and online help. Oracle Applications System Administrator's Guide
- Maintenance provides information for frequent tasks such as monitoring your system
with Oracle Applications Manager, managing concurrent managers and reports, using
diagnostic utilities, managing profile options, and using alerts. Oracle Applications
System Administrator's Guide - Security describes User Management, data security,
function security, auditing, and security configurations.

Oracle Applications Flexfields Guide


This guide provides flexfields planning, setup, and reference information for the Oracle
Applications implementation team, as well as for users responsible for the ongoing
maintenance of Oracle Applications product data. This guide also provides information
on creating custom reports on flexfields data.
Oracle Cash Management User Guide:
This guide describes how to use Oracle Cash Management to clear your receipts, as well
as reconcile bank statements with your outstanding balances and transactions. This
manual also explains how to effectively manage and control your cash cycle. It provides
comprehensive bank reconciliation and flexible cash forecasting.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

vii

Oracle General Ledger Implementation Guide:


This guide provides information on how to implement Oracle General Ledger. Use this
guide to understand the implementation steps required for application use, including
how to set up Accounting Flexfields, Accounts, and Calendars.
Oracle General Ledger Reference Guide:
This guide provides detailed information about setting up General Ledger Profile
Options and Applications Desktop Integrator (ADI) Profile Options.
Oracle General Ledger User's Guide:
This guide provides information on how to use Oracle General Ledger. Use this guide
to learn how to create and maintain ledgers, ledger currencies, budgets, and journal
entries. This guide also includes information about running financial reports.
Oracle Payables User Guide:
This guide describes how to use Oracle Payables to create invoices and make payments.
In addition, it describes how to enter and manage suppliers, import invoices using the
Payables open interface, manage purchase order and receipt matching, apply holds to
invoices, and validate invoices. It contains information on managing expense reporting,
procurement cards, and credit cards. This guide also explains the accounting for
Payables transactions.
Oracle Payables Implementation Guide:
This guide provides you with information on how to implement Oracle Payables. Use
this guide to understand the implementation steps required for how to set up suppliers,
payments, accounting, and tax.
Oracle Payables Reference Guide:
This guide provides you with detailed information about the Oracle Payables open
interfaces, such as the Invoice open interface, which lets you import invoices. It
also includes reference information on purchase order matching and purging
purchasing information.
Oracle Receivables User Guide:
This guide provides you with information on how to use Oracle Receivables. Use this
guide to learn how to create and maintain transactions and bills receivable, enter and
apply receipts, enter customer information, and manage revenue. This guide also
includes information about accounting in Receivables. Use the Standard Navigation
Paths appendix to find out how to access each Receivables window.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

viii

Oracle Receivables Implementation Guide:


This guide provides you with information on how to implement Oracle
Receivables. Use this guide to understand the implementation steps required for
application use, including how to set up customers, transactions, receipts,
accounting, tax, and collections. This guide also includes a comprehensive list of
profile options that you can set to customize application behavior.
Oracle Receivables Reference Guide:
This guide provides you with detailed information about all public application
programming interfaces (APIs) that you can use to extend Oracle Receivables
functionality. This guide also describes the Oracle Receivables open interfaces, such as
AutoLockbox which lets you create and apply receipts and AutoInvoice which you can
use to import and validate transactions from other systems. Archiving and purging
Receivables data is also discussed in this guide.

1.3.8 Integration Repository


The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.

1.3.9 Do Not Use Database Tools to Modify Oracle Applications Data


Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle Applications data unless
otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle Applications data, you risk destroying the integrity of your
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

ix

data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using an
Oracle Applications form can update many tables at once. But when you modify Oracle
Applications data using anything other than Oracle Applications, you may change a
row in one table without making corresponding changes in related tables. If your tables
get out of synchronization with each other, you risk retrieving erroneous information
and you risk unpredictable results throughout Oracle Applications.

When you use Oracle Applications to modify your data, Oracle Applications
automatically checks that your changes are valid. Oracle Applications also keeps track
of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track
who has changed your information because SQL*Plus and other database tools do not
keep a record of changes.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

Content

CHAPTER 1

1.1

Document Control ........................................................................................ ii

1.2

Send us Your Comments ............................................................................ iii

1.3

Preface ........................................................................................................... iv

LAD Add-on Localizations

Intended Audience .............................................................................. iv

1.3.2

Deaf/Hard of Hearing Access to Oracle Support Services ......... v

1.3.3

Documentation Accessibility ........................................................... v

1.3.4

Accessibility of Code Examples in Documentation ................... v

1.3.5

Accessibility of Links to External Web Sites in Documentation


vi

1.3.6

Structure ................................................................................................ vi

1.3.7

Related Information Sources................................................................ vi

1.3.8

Integration Repository ...................................................................... ix

1.3.9

Do Not Use Database Tools to Modify Oracle Applications Data


ix

Overview ........................................................................................................... 1
1.4

CHAPTER 2

1.3.1

Environment Setup ....................................................................................... 3

Middleware Configuration .............................................................................. 4


1.4.1

Weblogic Data Source Configuration ............................................. 4

1.4.2

Connection Pool: DbAdapter............................................................ 9

1.5

Deploy BPEL Processes ............................................................................. 15

1.6

E-Business Suite Setting Up Profile Options ................................................ 17

1.7

Deploy to SOA Server ................................................................................... 17

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xi

CHAPTER 3

PeopleSoft ....................................................................................................... 19
Introduction .............................................................................................................. 19
1.7.1

Apply Project ........................................................................................ 19

1.7.2

Set Message Schemas ........................................................................... 21

1.7.3

Export Web Services ............................................................................ 31

1.7.4

Check Outbound Endpoint URL........................................................ 36

1.7.5

Check Security ...................................................................................... 37

1.8

Pre Requisites .............................................................................................. 38

1.9

PeopleSoft Integration Broker Setup ........................................................ 38


1.9.1

Gateway Setup ...................................................................................... 38

1.9.2

Service Configuration .......................................................................... 42

1.9.3

Domain Configuration......................................................................... 43

1.9.4

Nodes Configuration ........................................................................... 43

1.10

Account ........................................................................................................ 50

1.10.1 Request and Response Message ........................................................ 50


1.10.2 Service ................................................................................................... 54
1.10.3 Service Operation ................................................................................ 54
1.10.4 .................................................................................................................... 57
1.10.5 Provide Web Service ........................................................................... 57
1.11

Cost Center .................................................................................................. 60

1.11.1 Pre Requisite......................................................................................... 60


1.11.2 Request and Response Message ........................................................ 60
1.11.3 Service ................................................................................................... 64
1.11.4 Service Operation ................................................................................ 65
1.11.5 Provide Web Service ........................................................................... 67
1.12

Company ...................................................................................................... 70

1.12.1 Request and Response Message ........................................................ 70


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xii

1.12.2 Service ................................................................................................... 74


1.12.3 Component Interface .......................................................................... 74
1.12.4 Service Operation ................................................................................ 75
1.12.5 Provide Web Service ........................................................................... 78
1.13

Establishment .............................................................................................. 81

1.13.1 Request and Response Message ........................................................ 81


1.13.2 Service ................................................................................................... 86
1.13.3 Component Interface .......................................................................... 86
1.13.4 Service Operation ................................................................................ 87
1.13.5 Provide Web Service ........................................................................... 90
1.14

Accounting ................................................................................................... 93

1.14.1 Import BPEL WebService ................................................................... 93


1.14.2 Rename Imported Objects .................................................................. 96
1.14.3 Service Operation GP_POST_GL ................................................... 98
1.14.4 Service Operation CLLEBS_ACCOUNTING_SYNC ................ 100
1.14.5 Queue Setup ....................................................................................... 102
1.14.6 Batch Publish Rules ........................................................................... 103
1.15

JobCode ...................................................................................................... 105

1.15.1 Import BPEL WebService ................................................................. 105


1.15.2 Rename Imported Objects ................................................................ 108
1.15.3 Service Operation CLLEBS_JOB_SYNC ...................................... 110
1.16

Organization .............................................................................................. 112

1.16.1 Import BPEL WebService ................................................................. 112


1.16.2 Rename Imported Objects ................................................................ 115
1.16.3 Service Operation CLLEBS_ORGANIZATION_SYNC ............ 117
1.17

Position ....................................................................................................... 119

1.17.1 Import BPEL WebService ................................................................. 119


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xiii

1.17.2 Rename Imported Objects ................................................................ 122


1.17.3 Service Operation CLLEBS_POSITION_SYNC ......................... 124
1.18

Bank and Branches.................................................................................... 126

1.18.1 Request and Response Message ...................................................... 126


1.18.2 Service ................................................................................................. 130
1.18.3 Service Operation .............................................................................. 131
1.18.4 Provide Web Service ......................................................................... 133
1.19

Employee.................................................................................................... 135

1.19.1 Import BPEL WebService ................................................................. 135


1.19.2 Rename Imported Objects ................................................................ 138
1.19.3 Service Operation CLLEBS_EMPLOYEE_SYNC ....................... 140
1.20

Employee Bank and Account .................................................................. 142

1.20.1 Import BPEL WebService ................................................................. 142


1.20.2 Rename Imported Objects ................................................................ 145
1.20.3 Service Operation CLLEBS_EMPL_BANK_ACCT_SYNC ....... 147
1.21

SEFIP Autonomous................................................................................... 149

1.21.1 Request and Response Message ...................................................... 149


1.21.2 Service ................................................................................................. 152
1.21.3 Service Operation .............................................................................. 153
1.21.4 Provide Web Service ......................................................................... 155
1.22

Accounting Header................................................................................... 158

1.22.1 Request and Response Message ...................................................... 158


1.22.2 Service ................................................................................................. 161
1.22.3 Service Operation .............................................................................. 161
1.22.4 Provide Web Service ......................................................................... 163
1.23

Accounting Results ................................................................................... 166

1.23.1 Request and Response Message ...................................................... 166


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xiv

1.23.2 Service ................................................................................................. 169


1.23.3 Service Operation .............................................................................. 169
1.23.4 Provide Web Service ......................................................................... 172
1.24

GL Business Unit....................................................................................... 174

1.24.1 Create Portal Registry ....................................................................... 174


1.24.2 Set Permission .................................................................................... 179
1.25

Controlling Area ....................................................................................... 182

1.25.1 Update Object in Application Designer ......................................... 182


1.25.2 Set Permission .................................................................................... 186
1.25.3
CHAPTER 4

Oracle PeopleSoft Setup ................................................................. 187

Configuring Oracle E-Business Suite .......................................................... 198


1.26

Setting Up Integration: EBS-PeopleSoft HCM Integration ................. 198

1.26.1 Setting Up GL Ledger to PSFT ........................................................ 198


1.26.2 Setting Up HRMS Parameter to PSFT ............................................ 199
1.26.3 Setting Up Establishment Parameters ............................................ 206
1.26.4 Setting Up Lookup Codes ................................................................ 206
1.26.5 Setting Up Payroll Definition .......................................................... 208
1.27

Setting Up: Oracle E-Business Suite Supplier Sites Extensions .......... 208

1.27.1 Monitoring Payroll Interface from PSFT ........................................ 213


1.27.2 Concurrents ........................................................................................ 214
1.27.3 Concurrents Sets ................................................................................ 215
1.27.4 Lookups .............................................................................................. 215
1.27.5 CLL_F357_HR_ADDRESS_TYPE ................................................... 215
1.27.6 CLL_F357_HR_ENTITY_TYPE ....................................................... 216
1.27.7 CLL_F357_HR_GENDER ................................................................. 216
1.27.8 CLL_F357_HR_MARITAL_STATUS .............................................. 216
1.27.9 CLL_F357_HR_NATIONALITY ..................................................... 217
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xv

1.27.10 CLL_F357_HR_PERSON_TYPE .................................................... 218


1.27.11 CLL_F357_HR_PHONE_TYPE ..................................................... 218
1.27.12 CLL_F357_PSFT_BANK ................................................................. 218
1.27.13 CLL_F357_PSFT_COA .................................................................... 219
1.27.14 CLL_F357_PSFT_EMPLOYEE ....................................................... 219
1.27.15 CLL_F357_PSFT_JOB ...................................................................... 219
1.27.16 CLL_F357_PSFT_POSITION.......................................................... 220
1.27.17 CLL_F357_GL_ACCT_HEADER_STATUS ................................. 220
1.27.18 CLL_F357_PSFT_LANGUAGES ................................................... 220
1.27.19 Hook GL Extensions ....................................................................... 221
1.27.20 Hook HR Extensions ....................................................................... 222
CHAPTER 5

Table Definition ........................................................................................... 225


Table Definition ...................................................................................................... 225
CLL_F357_ACCT_CC_POLLING ................................................................. 225
CLL_F357_BANKS_POLLING ...................................................................... 227
CLL_F357_BANK_BRANCHES_POLLING ................................................ 228
CLL_F357_GL_PARAMETERS ..................................................................... 231
CLL_F357_HR_PARAMETERS ..................................................................... 234
CLL_F357_LE_COMPANY_POLLING ........................................................ 238
CLL_F357_LE_ESTAB_POLLING ................................................................ 240
CLL_F357_LE_PARAMETERS ...................................................................... 242
CLL_F357_LE_REGIST_POLLING ............................................................... 243
CLL_F357_LOG ............................................................................................... 245
CLL_F357_POLLING_CONTROL ................................................................ 246
CLL_F357_REFERENCES .............................................................................. 247
CLL_F357_SUPPLIER_SITES_EXT ............................................................... 249

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xvi

CLL_F357_GL_ACCOUNTING_HEADERS ............................................... 250


CLL_F357_GL_ACCOUNTING_LINES ...................................................... 251
CLL_F357_GL_ACCOUNTING_OCCURS ................................................. 256

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration - Implementation Guide

Preface

xvii

CHAPTER

Overview
PeopleSoft Global Payroll currently integrates completely with PeopleSoft
Enterprise Financials . The chart of accounts, GL Business Unit details all come
from PeopleSoft Enterprise Financials.
There is a need to have similar full integration with Oracle EBS Financials (GL).
The feature has functional dependencies on Oracle General Ledger Setup,
PeopleSoft HCM setup and PeopleTools. More details on the feature can be found
in this document. This integration involves the following components on the
PeopleSoft HCM end:

Associate GL Business Unit (GLBU) to Ledger;

Map existing Chartfields to Flexfield segments from in Oracle GL;

Modify existing chartfield pages to support changes;

Transfer

Accounting Lines (CLLEBS_GL_ACCOUNT_REQUEST and

CLLEBS_GL_ACCOUNT_RESPONSE) to Oracle GL Interface.

To achieve this integration with Oracle EBS Financials there is a need to


development some web services.
This guide, details the technical details on developing web services to achieve this.
There are two enhancements to achieve the objective to new model of the
integration between PSFT and Oracle EBS, more specifically the accounting of
payroll from PSFT to GL:

BUG 20002148 - EBS X PEOPLE INTEGRATION - SEND ACCOUNT /


COST CENTER TO PSFT: modify the way data out of Oracle EBS and arrive
in PSFT tables.

BUG 19510312 - ER: EBS X PEOPLE INTEGRATION - UNBALANCED


RECORDS FOR EBS/GL: modify the input data into Oracle EBS General
Ledgers to new tables, creation of a monitor data on Oracle EBS and PSFT
systems and new routines to manipulate data and loading this data on
Oracle EBS General Ledgers.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

Architecture

Figure 1: Functional Illustration

The above diagram provides high level details of PeopleSoft HCM Global
Payroll to Oracle Financials GL integration

Figure 2: Technical Illustration

The above diagram illustrates the Technical approach for PeopleSoft HCM
Global Payroll to Oracle Financials GL integration.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

1.4 Environment Setup

The following is the Environment setup used for the purpose of this Technical Document;

1.

Oracle SOA Suite 11g (11.1.1.3.0) Patch Set 2.

2.

Oracle JDeveloper 11g (11.1.1.3.0).

3.

PeopleSoft HCM 9.0 with People Tools 8.49 (release 20 and above).

4. Oracle E-Business Suite R12 with Oracle Financials Release Update Pack 6
(R12.FIN_PF.A.DELTA.6).

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

CHAPTER

Middleware Configuration
This section describes the changes required to middleware files following
installation. It provides the required steps for post-installation configuration for the
Oracle Weblogic Enterprise Manager.

The BPEL processes are defined in jar files on My Oracle Support.


Patch 21762774 is required to deploy the BPEL flows for this integration.
These processes cannot be seeded within Oracle Weblogic Enterprise Manager.
They require manual deployment through the Oracle Weblogic Enterprise
Manager Console.

Note:

The

examples

shown

include

values

for

demonstration purposes. Actual values may need to be


entered manually to override a default value. Examples of
such values include DB Host Name and Port.

1.4.1 Weblogic Data Source Configuration

Follow these steps to configure the adapters. First create the data source and then a
connection pool for that data source. Use the WebLogic Server console:

Database Connection: EBS Data Source


1. Open

http://hostname:port/console to start the console and login using


weblogic/xxxxx. Replace the host, port and username/password to match your own
configuration.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

2. On the left navigation bar, select Services > JDBC > Data Sources. In the data source

table, select New.

3. Enter the data source information and select Next.


Name

Value

Name:

CllEbsDS (You must use this name)

JNDI Name:

jdbc/CllEbsDS (You must use this name)

Database Type:

Oracle

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

4. The Database driver defaults to the correct driver: Oracles Driver (Thin XA) for

Instance connections. Select Next.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

5. Select Next again.

6. Enter the database information and select Next.


Name

Value

Database Name:

sid (set according to your configuration)

Host name:

hostname (set according to your configuration)

Port:

port (set according to your configuration)

Database user name:

apps

Database user password:

****

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

7. Select Test Configuration.

Confirm success message at top of page.


Select Next.

8. Select Target server where your SOA component is running soa_server1 and

AdminServer. Select Finish.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

1.4.2 Connection Pool: DbAdapter


Now create the DBAdapter connection pool. You have to edit the DbAdapter
application.

9. In the left navigation bar, select Deployments. Then, select the DbAdapter

application (select the name, not the checkbox)

10. Select the Configuration tab, and then select the Outbound Connection Pools tab.

Select New.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

11. Select the radio button for javax.resource.cci.ConnectionFactory and select Next.

12. Enter the JNDI Name as follows: eis/DB/CllEbsDS (You must use this name)

Note that this is not the same value as in step 3 above. It must match the value you
enter in your database connection you create when building your application later.
Select Finish.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

10

13. Expand the connection factory and select your new connection pool (select the name,

not the checkbox)

14. In the Properties table, select the value listed for xADataSource and replace it with

your data source you created above: jdbc/CllEbsDS. Press ENTER key to apply the
value. Select Save.
You must use the ENTER key for the value to be entered in the field. You must use
the Save button to save the value.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

11

15. Go back to the main Deployments page to Update the DbAdapter:

Select Deployments in the left navigation bar.


Select the checkbox next to DbAdapter.
Select Update.

16. Select Redeploy this application and confirm the deployment plan location.

Select Finish.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

12

17. Expand the connection factory and select your new connection pool (select the name,

not the checkbox)

18. In the Properties table, select the value listed for xADataSource and replace it with

your data source you created above: jdbc/CllEbsDS. Press ENTER key to apply the
value. Select Save.
You must use the ENTER key for the value to be entered in the field. You must use
the Save button to save the value.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

13

19. Go back to the main Deployments page to Update the DbAdapter:

Select Deployments in the left navigation bar.


Select the checkbox next to DbAdapter.
Select Update.

20. Select Redeploy this application and confirm the deployment plan location.

Select Finish.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

14

1.5 Deploy BPEL Processes


The BPEL processes is defined in jar files on My Oracle Support patch: 21762774.
You will find those files inside CllEbsPsftBundle.zip. The bundle file must be deployed in the
following order:
1. CllEbsPsftBundle.zip
These processes cannot be seeded within Oracle Weblogic Enterprise Manager. They require
manual deployment through the Oracle Enterprise Manager.

Prerequisites
Create the cll partition.
1.

Open http://hostname:port/em to start the Oracle Enterprise Manager and login using
weblogic/xxxx. Replace the host, port and username/password to match your own
configuration.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

15

2.

Select Farm_base_domain > SOA > soa-infra.

3.

In the soa-infra page, drop down the SOA Infrastructure menu and select Manage
Partitions.
Select Create to create a new partition.

4.

In the Use cll as the Name and select create.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

16

1.6 E-Business Suite Setting Up Profile Options

During implementation, you set a value for each user profile option to specify how
LAD Add-on Localizations EBS-PeopleSoft HCM Integration controls access to and processes
data. Generally,
the system administrator sets and updates profile values. See: Setting User Profile
Options, Oracle Applications System Administrator's Guide.

CLL_F357: URL for the SOA Suite for EBS-PSFT Integration


========================================================
http://<hostname>:<port>/soa-infra/services/cll

CLL_F357: URL for the PeopleSoft Integration Broker for EBS-PSFT Integration
============================================================================
http://<hostname>:<port>/PSIGW/PeopleSoftServiceListeningConnector

1.7 Deploy to SOA Server


On Oracle Enterprise Manager...
1.

Select Farm_base_domain > SOA > soa-infra > cll.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

17

2.

Select Deployment > Deploy to This Partition...


In the next page, select Archive is on the machine where this web browser is running.
and browse for the SOA bundle file CllEbsPsftBundle.zip.
Click Next.

3.

LAD Add-on Localizations

Select Deploy.

EBS-PeopleSoft HCM Integration- Implementation Guide

18

CHAPTER

PeopleSoft

Introduction

This chapter describes the steps needed to apply this integration as a project.
The steps are:

Apply the project (import as a file)

Set Message Schemas

Export Web Services

Check outbound endpoint URL

Check security

1.7.1 Apply Project

The first step is to apply the project. The project was exported as a file from
PeopleSoft and can be used to import most of the objects. Some of then need
to be adjusted in the next steps.

Download the files below from My Oracle Support Note : 1166388.1


upd16477363.zip
upd16617037.zip
upd16701506.zip
upd16909033.zip
upd18551247.zip
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

19

upd19510312.zip
Unzip it in a folder of your choice
Apply the project using Change Assistant tool
Set Change Assistant Options to Apply Application Update

Set Apply with Database Compare/Copy and proced with forward steps

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

20

1.7.2 Set Message Schemas

After you copy the project, you need to set the message schemas (for those that are not based in record).
To do that, login and go to Home > PeopleTools > Integration Broker > Integration Setup > Messages
This is needed because the schema was not copied.
Bellow are all the messages that need to be changed and their schema

CLLEBS_ACCOUNTING_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveAccountingFromPSFT/CllReceiveAccountingFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceiveaccountingfrompsftebs_client_ep?XSD=xsd/CllReceive
AccountingFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/ebo/AccountingEBO"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/ebo/AccountingEBO.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

21

CLLEBS_ACCOUNTING_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveAccountingFromPSFT/CllReceiveAccountingFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceiveaccountingfrompsftebs_client_ep?XSD=xsd/CllReceive
AccountingFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/ebo/AccountingEBO"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/ebo/AccountingEBO.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

CLLEBS_BANKBRANCHES_REQUEST
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/BankBranches"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/BankBranches" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Bank" type="BankType"/>
<xsd:complexType name="BankType">
<xsd:sequence>
<xsd:element minOccurs="0" name="BankCountryCode" type="xsd:string"/>
<xsd:element minOccurs="0" name="BankId" type="xsd:string"/>
<xsd:element minOccurs="0" name="Status" type="xsd:string"/>
<xsd:element minOccurs="0" name="BankName" type="xsd:date"/>
<xsd:element minOccurs="0" name="BankIdCode" type="xsd:string"/>
<xsd:element minOccurs="0" name="Country" type="xsd:string"/>
<xsd:element minOccurs="0" name="Address1" type="xsd:string"/>
<xsd:element minOccurs="0" name="Address2" type="xsd:string"/>
<xsd:element minOccurs="0" name="Address3" type="xsd:string"/>
<xsd:element minOccurs="0" name="Address4" type="xsd:string"/>
<xsd:element minOccurs="0" name="Num" type="xsd:string"/>
<xsd:element minOccurs="0" name="State" type="xsd:int"/>
<xsd:element minOccurs="0" name="City" type="xsd:string"/>
<xsd:element minOccurs="0" name="PostalCode" type="xsd:string"/>
<xsd:element minOccurs="0" name="Phone" type="xsd:string"/>
<xsd:element minOccurs="0" name="Branches" type="BranchCollection"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="BranchCollection">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Branch" type="Branch"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Branch">
<xsd:sequence>
<xsd:element minOccurs="0" name="BranchId" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchName" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchStatus" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchCountry" type="xsd:date"/>
<xsd:element minOccurs="0" name="BranchAddress1" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchAddress2" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchAddress3" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchAddress4" type="xsd:string"/>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

22

<xsd:element minOccurs="0" name="BranchNum" type="xsd:string"/>


<xsd:element minOccurs="0" name="BranchState" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchCity" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchPostalCode" type="xsd:int"/>
<xsd:element minOccurs="0" name="BranchPhone" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchBankIdCode" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchCheckDigit" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchLocal" type="xsd:string"/>
<xsd:element minOccurs="0" name="BranchContactName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

CLLEBS_BANKBRANCHES_RESPONSE
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/BankBranches"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/BankBranches" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

CLLEBS_COMPANY_REQUEST
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Company" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="CompanyDefn">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Company" type="Company"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Company">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="COMPANYID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="BEGIN_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="END_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="EFF_STATUS" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCRSHORT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DEFAULT_SETID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="COUNTRY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS1" type="xsd:string"/>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

23

<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS2" type="xsd:string"/>


<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS3" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS4" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="NUM1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="CITY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="STATE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="POSTAL" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="REG_REGION" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

CLLEBS_COMPANY_RESPONSE
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Company" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Company" type="CompanyResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="CompanyResponse">
<xsd:sequence>
<xsd:element name="COMPANYID" type="xsd:string"/>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

CLLEBS_COST_CENTER_REQUEST
<?xml version= '1.0' encoding= 'UTF-8' ?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns="http://xmlns.oracle.com/cll/ebo/CostCenter" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Language">
<xsd:sequence>
<xsd:element name="Language" type="languageType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="languageType">
<xsd:sequence>
<xsd:element name="IsoCode" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Description"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

24

<xsd:element name="CostCenter">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Ledger" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Value" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Languages"
type="Language"/>
<xsd:element maxOccurs="1" minOccurs="0" name="StartDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="EndDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="LastUpdateDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Type" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="ChartOfAccount" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

CLLEBS_COST_CENTER_RESPONSE
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns="http://xmlns.oracle.com/cll/ebo/CostCenter" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

CLLEBS_EMPLOYEE_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveEmployeeFromPSFT/CllReceiveEmployeeFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/cllreceiveemployeefrompsftebs_client_ep?XSD=xsd/CllReceiveE
mployeeFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/apps/cll/xsd/addressing.xsd"/>
</schema>

CLLEBS_EMPLOYEE_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

25

<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveEmployeeFromPSFT/CllReceiveEmployeeFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/cllreceiveemployeefrompsftebs_client_ep?XSD=xsd/CllReceiveE
mployeeFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeFromPSFT/apps/cll/xsd/addressing.xsd"/>
</schema>

CLLEBS_EMPL_BANK_ACCT_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveEmployeeBankAccountFromPSFT/CllReceiveEmployeeBankAc
countFromPSFTEBS" schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeBankAccountFromPSFT/cllreceiveemployeebankaccountfrompsftebs_client_
ep?XSD=xsd/CllReceiveEmployeeBankAccountFromPSFTEBS.xsd"/>
</schema>

CLLEBS_EMPL_BANK_ACCT_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveEmployeeBankAccountFromPSFT/CllReceiveEmployeeBankAc
countFromPSFTEBS" schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveEmployeeBankAccountFromPSFT/cllreceiveemployeebankaccountfrompsftebs_client_
ep?XSD=xsd/CllReceiveEmployeeBankAccountFromPSFTEBS.xsd"/>
</schema>

CLLEBS_ESTABLISHMENT_REQUEST
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Establishment" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EstablishmentDefn">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Establishment" type="Establishment"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Establishment">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="ESTABID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="BEGIN_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="END_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="EFF_STATUS" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="HQUNIT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCRSHORT" type="xsd:string"/>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

26

<xsd:element maxOccurs="1" minOccurs="1" name="COMPANY" type="xsd:string"/>


<xsd:element maxOccurs="1" minOccurs="1" name="REG_REGION" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="COUNTRY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS2" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS3" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS4" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="NUM1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="CITY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="STATE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="POSTAL" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="ESTAB_BRA_TBL" type="ESTAB_BRA_TBL"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ESTAB_BRA_TBL">
<xsd:sequence>
<xsd:element name="COUNTY_CD_BRA" type="xsd:string"/>
<xsd:element name="COMP_INS_TYPE_BRA" type="xsd:string"/>
<xsd:element name="ESTAB_ASOC_BRA" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="ESTAB_ID_BRA" type="ESTAB_ID_BRA"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ESTAB_ID_BRA">
<xsd:sequence>
<xsd:element name="ESTAB_ID_TYPE_BRA" type="xsd:string"/>
<xsd:element name="ESTABID_BRA" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

CLLEBS_ESTABLISHMENT_RESPONSE
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Establishment" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Establishment"
type="EstablishmentResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="EstablishmentResponse">
<xsd:sequence>
<xsd:element name="ESTABID" type="xsd:string"/>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

27

CLLEBS_GL_ACCOUNT_REQUEST
<?xml version= '1.0' encoding= 'UTF-8' ?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccount" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Language">
<xsd:sequence>
<xsd:element name="Language" type="languageType"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="languageType">
<xsd:sequence>
<xsd:element name="IsoCode" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Description"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="GLAccount">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Ledger" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Value" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Languages" type="Language"/>
<xsd:element maxOccurs="1" minOccurs="0" name="StartDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="EndDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="LastUpdateDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Type" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="ChartOfAccount" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

CLLEBS_GL_ACCOUNT_RESPONSE
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccount" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

CLLEBS_JOBCODE_REQUEST

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

28

<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/cll/CllReceiveJobsFromPSFT/CllReceiveJobsFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveJobsFromPSFT/cllreceivejobsfrompsftebs_client_ep?XSD=xsd/CllReceiveJobsFromPSF
TEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveJobsFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

CLLEBS_JOBCODE_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/cll/CllReceiveJobsFromPSFT/CllReceiveJobsFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveJobsFromPSFT/cllreceivejobsfrompsftebs_client_ep?XSD=xsd/CllReceiveJobsFromPSF
TEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveJobsFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

CLLEBS_ORGANIZATION_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveOrganizationsFromPSFT/CllReceiveOrganizationsFromPSFTEB
S" schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveOrganizationsFromPSFT/cllreceiveorganizationsfrompsftebs_client_ep?XSD=xsd/CllR
eceiveOrganizationsFromPSFTEBS.xsd"/>
</schema>

CLLEBS_ORGANIZATION_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceiveOrganizationsFromPSFT/CllReceiveOrganizationsFromPSFTEB
S" schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceiveOrganizationsFromPSFT/cllreceiveorganizationsfrompsftebs_client_ep?XSD=xsd/CllR
eceiveOrganizationsFromPSFTEBS.xsd"/>
</schema>

CLLEBS_POSITION_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceivePositionsFromPSFT/CllReceivePositionsFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceivePositionsFromPSFT/cllreceivepositionsfrompsftebs_client_ep?XSD=xsd/CllReceivePos
itionsFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceivePositionsFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

29

CLLEBS_POSITION_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/cll/CllReceivePositionsFromPSFT/CllReceivePositionsFromPSFTEBS"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceivePositionsFromPSFT/cllreceivepositionsfrompsftebs_client_ep?XSD=xsd/CllReceivePos
itionsFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://brdell31.br.oracle.com:8001/soainfra/services/cll/cll_ReceivePositionsFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

CLLEBS_GL_ACCTG_RESUL_REQUEST
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccountingResult" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="GLAccountingResult">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayrollId" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="StatusFlag" type="xsd:string"/>
<xsd:element minOccurs="0" name="ErrorText" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

CLLEBS_GL_ACCTG_RESUL_RESPONSE
<?xml version= '1.0' encoding= 'UTF-8' ?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

30

CLLEBS_ACCOUNTING_HDR_REQUEST
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/F357/CllReceiveAccountingFromPSFT/CllReceivePayrollHeaderFromPSFTE
BS" schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceivepayrollheaderfrompsftebs_client_ep?XSD=xsd/CllRece
ivePayrollHeaderFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

CLLEBS_ACCOUNTING_HDR_RESPONSE
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/F357/CllReceiveAccountingFromPSFT/CllReceivePayrollHeaderFromPSFTE
BS" schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceivepayrollheaderfrompsftebs_client_ep?XSD=xsd/CllRece
ivePayrollHeaderFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

1.7.3 Export Web Services

The next step is to export webservices (regenerate WSDL).


Go to Home > PeopleTools > Integration Broker > Web Services > Provide Web Service
Set service name to CLL and click Search

A list with all services starting with CLL will show up.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

31

Select the services bellow and click Next

CLLEBS_ACCOUNTING

CLLEBS_ACCOUNTING_HDR

CLLEBS_AUTON_SEFIP

CLLEBS_BANKBRANCHES

CLLEBS_COMPANY

CLLEBS_COST_CENTER

CLLEBS_ESTABLISHMENT

CLLEBS_GL_ACCOUNT

CLLEBS_GL_ACCOUNTING_RESULTS

Seelct all checkboxes the appear in the screen below and click Next

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

32

Click Next

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

33

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

34

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

35

1.7.4 Check Outbound Endpoint URL

Review the outbound web services endpoint URL to see if they point to the right SOA Server.
Go to Home > PeopleTools > Integration Broker > Integration Setup > Service Operation.
Search for the services operations bellow:

CLLEBS_ACCOUNTING_SYNC

CLLEBS_EMPLOYEE_SYNC

CLLEBS_EMPL_BANK_ACCT_SYNC

CLLEBS_ORGANIZATION_SYNC

CLLEBS_POSITION_SYNC

CLLEBS_ACCOUNTING_HDR_SYNC

For each operation listed above go to the routing tab and select the active route

Go to Connector Properties tab and set the URL to point to your SOA Server.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

36

1.7.5 Check Security

The last step is to check the security and set it according to the company policies.
The user set in the local node muast have access to all web services (full access) and for the component
interfaces (full access).

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

37

1.8 Pre Requisites

This sections describes some pre requisites necessary to configure the integration
To have applied peoplesoft project updCLL_PRJ16477363.zip and
CLL_PRJ19510312.zip on your environment.
1.9 PeopleSoft Integration Broker Setup

This sections describes the steps needed to configure PeopleSoft Integration Broker.

1.9.1 Gateway Setup


The first step is to configure the gateway.
Go to: Home > PeopleTools > Integration Broker > Configuration > Gateways
Search for the local gateway. Usually called LOCAL.

Setup the gateway URL. The most common is to use the same as the web
application.
The URL looks like this:
HTTP://<server>[:<port>]/PSIGW/PeopleSoftListeningConnector.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

38

When you change you gateway URL, all the connectors will be reloaded.

Click OK.
All the connectors will be removed. Thats fine.

To check if the URL is OK, click on Ping Gateway. The screen above should pop
up.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

39

The tools version may differ, but all the other message should be the same. Check if
the status is ACTIVE.
If the page opened. Than you selected a valid URL. You can now load the
connectors.
Click on Load Gateway Connectors to load all the default connectors installed.
A message Box is shown with the load status

The screen below show all the connectors that came with PeopleSoft. Other may
exists that were developed internally and are not shown here.

After load the connectors, click on Gateway Setup Properties

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

40

Use the default user id (administrator) and the default password (password)

Configure the gateway default app Server and the local node. You can get this
information with your Server administrator or typing Ctrl + J to get the
application information.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

41

Save.

1.9.2 Service Configuration


Go to: Home > PeopleTools > Integration Broker > Service Configuration

Here is possible to configure the default Service Namespace and Schema


Namespace and the Target Location for webservice calls.
Its only necessary to configure the Target Location. You can change the other
parameters, but its not necessary.
For the target location follow the example that exists in the page: Erro! A referncia
de hiperlink no vlida..

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

42

1.9.3 Domain Configuration


Home > PeopleTools >Integration Broker > Service Operations Monitor >
Administration > Domain Status
In this page is necessary to activate your domain.

It should look like this after the domain is active.

1.9.4 Nodes Configuration


Home > PeopleTools > Integration Broker > Integration Setup > Nodes
We need to configure three nodes.
The local node
The Anonymous Node
The BPEL Node

1.9.4.1.1 Local Node

Search for the local node. The local node is identified by two flags in the search as
shown in the screen

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

43

The default local node for the HR installation is PSFT_HR.


Select the local node. In the first tab is possible to define an authentication option.
Depending in the option selected you will need to define a Password.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

44

Set the Authentication Option, the Node Password and the Default User Id. Its not
recommended to use a super user as the Default User.
In the Connectors tab is set the connector id used by this node. The default
connector id for the local node is PSFTTARGET.

Click on Ping Node to test if the node is properly configured.

If you see this message, its because the node is working.


The others tab are not in the scope of this document.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

45

1.9.4.1.2 Anonymous Node

Search for the anonymous node.

Configure it as shown in the screens below.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

46

1.9.4.1.3 BPEL Node

Search for the BPEL node.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

47

Configure it as shown in the screens below.

In the BPEL node its necessary to setup the connection properties to access the
BPEL engine Server. To do this, click on Properties in the botton of the page.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

48

There are three default parameters in this page:


BPELCONSOLEURL: Set the URL to the BPEL console engine
BPELDOMAIN: Set the domain where the BPEL were deployed.
BPELDOMAINPWD: Not necessary (can leave it blank).
The connectors tab.

Note: From this point, there are two options to follow this document. Or
you can still read this chapter or skip it and go to chapter 6.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

49

1.10 Account
To create the account web services, follow these steps:
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.10.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_GL_ACCOUNT_REQUEST
Message Version: V2
Define the message as shown in the pictures

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

50

Message Schema:

<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Language">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Language" type="languageType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="languageType">
<xsd:sequence>
<xsd:element name="IsoCode" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Description" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="GLAccount">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Ledger" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Value" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Languages" type="Language"/>
<xsd:element maxOccurs="1" minOccurs="0" name="StartDate" type="xsd:date"/>
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

51

<xsd:element maxOccurs="1" minOccurs="0" name="EndDate" type="xsd:date"/>


<xsd:element maxOccurs="1" minOccurs="0" name="LastUpdateDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Type" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="ChartOfAccount" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Save.
Add a new Message
Message Name: CLLEBS_GL_ACCOUNT_RESPONSE
Message Version: V1
Define the message as shown in the pictures

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

52

Message Schema:

<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccount"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

53

1.10.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_GL_ACCOUNT
Define the service as shown

1.10.3 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_GL_ACCOUNT
Service Operation: CLLEBS_GL_ACCOUNT_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

54

Check the Active Flag


Check the routing action Generate Any-to-Local to add a routing accepting
request from anywhere.
Request Message: CLLEBS_GL_ACCOUNT_REQUEST.V2
Response Message: CLLEBS_GL_ACCOUNT_RESPONSE.V1
Handlers Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

55

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

Check if
Routing Type is Synch
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

56

Sender node is ~~Any~~


Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.
1.10.4

1.10.5 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_GL_ACCOUNT

Click the link Provide Web Service and follow the prints

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

57

Click Next

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

58

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

59

1.11 Cost Center


To create the cost center web services, follow these steps:
Pre Requisite
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

Obs: To perform a cost center validation on Payroll Run process apply the
project CLL_PRJ18551247.zip and follow the document EBS-PSFT Basic Steps Validao Centro de Custo POR.pdf.

1.11.1 Pre Requisite


To have applied peoplesoft project updCLL_PRJ16477363.zip,
CLL_PRJ18551247.zip and CLL_PRJ19510312.zip on your environment.

1.11.2 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_COST_CENTER_REQUEST
Message Version: V2
Define the message as shown in the pictures
Message Definition Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

60

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

61

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Language">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="Language" type="languageType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="languageType">
<xsd:sequence>
<xsd:element name="IsoCode" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Description" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="CostCenter">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Ledger" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Value" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Languages" type="Language"/>
<xsd:element maxOccurs="1" minOccurs="0" name="StartDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="EndDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="LastUpdateDate" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Type" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="ChartOfAccount" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Save.

Add a new Message


Message Name: CLLEBS_COST_CENTER_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

62

Schema Tab

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns="http://xmlns.oracle.com/cll/ebo/CostCenter"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

63

<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.

1.11.3 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_COST_CENTER
Define the service as shown

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

64

1.11.4 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_COST_CENTER
Service Operation: CLLEBS_COST_CENTER_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

Check the Active Flag

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

65

Check the routing action Generate Any-to-Local to add a routing accepting


request from anywhere.
Request Message: CLLEBS_COST_CENTER_REQUEST.V2
Response Message: CLLEBS_COST_CENTER_RESPONSE.V1
Handlers Tab

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

66

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.11.5 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_COST_CENTER

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

67

Click the link Provide Web Service and follow the prints

Click Next

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

68

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

69

1.12 Company
To create the company web services, follow these steps:
Define the request and response message
Define the Service
Define the Component Interface Used to Save the Company
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.12.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_COMPANY_REQUEST
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

70

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="CompanyDefn">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Company" type="Company"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Company">
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

71

<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="COMPANYID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="BEGIN_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="END_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="EFF_STATUS" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCRSHORT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DEFAULT_SETID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="COUNTRY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS2" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS3" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS4" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="NUM1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="CITY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="STATE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="POSTAL" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="REG_REGION" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Save.
Add a new Message
Message Name: CLLEBS_COMPANY_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

72

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Company"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Company"
type="CompanyResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="CompanyResponse">
<xsd:sequence>
<xsd:element name="COMPANYID" type="xsd:string"/>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

73

</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.

1.12.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_COMPANY
Define the service as shown

1.12.3 Component Interface

Its necessary to check if the component interface has the proper fields to work in
this integration.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

74

For this, we created a new component interface.


Component Interface Name: CLLEBS_COMPANY_TABLE_CI.
Component Interface Base Component Name: COMPANY_TABLE
Methods: Default (Cancel, Create, Find, Get, Save)
Properties (minimun required):
Level

Record

Field

Property Name

COMPANY_TBL

EFFDT

EFFDT

COMPANY_TBL

DESCR

DESCR

COMPANY_TBL

EFF_STATUS

EFF_STATUS

COMPANY_TBL

DESCRSHORT

DESCRSHORT

COMPANY_TBL

DEFAULT_SETID

DEFAULT_SETID

COMPANY_TBL

REG_REGION

REG_REGION

COMPANY_TBL

COUNTRY

COUNTRY_0

COMPANY_TBL

ADDRESS1

ADDRESS1_0

COMPANY_TBL

ADDRESS2

ADDRESS2_0

COMPANY_TBL

ADDRESS3

ADDRESS3_0

COMPANY_TBL

ADDRESS4

ADDRESS4_0

COMPANY_TBL

CITY

CITY_0

COMPANY_TBL

NUM1

NUM1_0

COMPANY_TBL

STATE

STATE_0

COMPANY_TBL

POSTAL

POSTAL_0

1.12.4 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_COMPANY
Service Operation: CLLEBS_COMPANY_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

75

Check the Active Flag


Check the routing action Generate Any-to-Local to add a routing accepting
request from anywhere.
Request Message: CLLEBS_COMPANY_REQUEST.V1
Response Message: CLLEBS_COMPANY_RESPONSE.V1
Handlers Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

76

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

Check if
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

77

Routing Type is Synch


Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.12.5 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_COMPANY

Click the link Provide Web Service and follow the prints
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

78

Click Next

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

79

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

80

1.13 Establishment
To create the establishment web services, follow these steps:
Define the request and response message
Define the Service
Define the Component Interface Used to Save the Establishment
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.13.1 Request and Response Message

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_ESTABLISHMENT_REQUEST
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

81

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

82

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EstablishmentDefn">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Establishment"
type="Establishment"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Establishment">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="ESTABID" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="BEGIN_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="END_DATE" type="xsd:date"/>
<xsd:element maxOccurs="1" minOccurs="1" name="EFF_STATUS" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="HQUNIT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="DESCRSHORT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="COMPANY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="REG_REGION" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="COUNTRY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS2" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS3" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="ADDRESS4" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="NUM1" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="CITY" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="STATE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="POSTAL" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="ESTAB_BRA_TBL"
type="ESTAB_BRA_TBL"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ESTAB_BRA_TBL">
<xsd:sequence>
<xsd:element name="COUNTY_CD_BRA" type="xsd:string"/>
<xsd:element name="COMP_INS_TYPE_BRA" type="xsd:string"/>
<xsd:element name="ESTAB_ASOC_BRA" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="ESTAB_ID_BRA"
type="ESTAB_ID_BRA"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ESTAB_ID_BRA">
<xsd:sequence>
<xsd:element name="ESTAB_ID_TYPE_BRA" type="xsd:string"/>
<xsd:element name="ESTABID_BRA" type="xsd:string"/>
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

83

</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Save.
Add a new Message
Message Name: CLLEBS_ESTABLISHMENT_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

84

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/Establishment"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Establishment"
type="EstablishmentResponse"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="EstablishmentResponse">
<xsd:sequence>
<xsd:element name="ESTABID" type="xsd:string"/>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

85

<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.

1.13.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_ESTABLISHMENT
Define the service as shown

1.13.3 Component Interface

Its necessary to check if the component interface has the proper fields to work in
this integration.
For this, we created a new component interface.
Component Interface Name: CLLEBS_ESTAB_TBL_BRA.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

86

Component Interface Base Component Name: ESTAB_TBL_BRA


Methods: Default (Cancel, Create, Find, Get, Save)
Properties (minimun required):
Level

Record

Field

Property Name

ESTAB_TBL

EFFDT

EFFDT_0

ESTAB_TBL

DESCR

DESCR_0

ESTAB_TBL

EFF_STATUS

EFF_STATUS

ESTAB_TBL

DESCRSHORT

HQUNIT

ESTAB_TBL

DEFAULT_SETID

DESCRSHORT

ESTAB_TBL

COMPANY

COMPANY

ESTAB_TBL

REG_REGION

REG_REGION

ESTAB_TBL

COUNTRY

COUNTRY_0

ESTAB_TBL

ADDRESS1

ADDRESS1_0

ESTAB_TBL

ADDRESS2

ADDRESS2_0

ESTAB_TBL

ADDRESS3

ADDRESS3_0

ESTAB_TBL

ADDRESS4

ADDRESS4_0

ESTAB_TBL

CITY

CITY_0

ESTAB_TBL

NUM1

NUM1_0

ESTAB_TBL

STATE

STATE_0

ESTAB_TBL

POSTAL

POSTAL_0

ESTAB_TBL_BRA COUNTY_CD_BRA

ESTAB_TBL_BRA COMP_INS_TYPE_BRA COMP_INS_TYPE_BRA

ESTAB_TBL_BRA ESTAB_ASOC_BRA

ESTAB_ASOC_BRA

ESTAB_ID_BRA

ESTAB_ID_TYPE_BRA

ESTAB_ID_TYPE_BRA

ESTAB_ID_BRA

ESTAB_ID_BRA

ESTAB_ID_BRA

COUNTY_CD_BRA

1.13.4 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_ESTABLISHMENT
Service Operation: CLLEBS_ESTABLISHMENT_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

87

Check the Active Flag


Check the routing action Generate Any-to-Local to add a routing accepting
request from anywhere.
Request Message: CLLEBS_ESTABLISHMENT_REQUEST.V1
Response Message: CLLEBS_ESTABLISHMENT_RESPONSE.V1
Handlers Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

88

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

89

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.13.5 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_ESTABLISHMENT

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

90

Click the link Provide Web Service and follow the prints

Click Next

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

91

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

92

1.14 Accounting
To send the chartfield combination from PeopleSoft to EBS using WebServices,
follow these steps:
Import BPEL WebService
Rename Imported Objects
Create the Handler Peoplecode
Alter the GP_POST_GL Service Operation
Queue Setup
Set Batch Publication Rules

1.14.1 Import BPEL WebService

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
http://<server>:<port>/<client specific
path>/CllReceiveAccountingFromPSFT/cllreceiveaccountingfrompsftebs_client_ep
?WSDL

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

93

Click Next
Select the Service to create (cllreceiveaccountingfrompsftebs_client_ep).

Click Next
Select the Services Operation do create.

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_ACCOUNTING_REQUEST
Response Message: CLLEBS_ACCOUNTING_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

94

Click Next
Select Use Existing Node and inform BPEL as the node

Click Finish.
A brief description of what was done is shown.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

95

1.14.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

Service: CLLRECEIVEACCOUNTINGFROMPSFTEB

New Name: CLLEBS_ACCOUNTING

Click on Rename

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

96

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_ACCOUNTING_SYNC

Click on Rename

The result should be: Operation Renamed


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

97

1.14.3 Service Operation GP_POST_GL

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: GP_POST_GL
Service Operation: GP_POST_GL
Operation Type: Asynchronous One Way
Alter the Operation as shown
General Tab
Verifiy if there is Local-to-Local routing created and if the Service Operation is
active.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

98

Handlers Tab

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

99

Check if
Routing Type is Asynch
Sender node is your local node (in this case PSFT_HR)
Receiver Node is your local node (in this case PSFT_HR)
Direction is Local
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.14.4 Service Operation CLLEBS_ACCOUNTING_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_ACCOUNTING
Service Operation: CLLEBS_ACCOUNTING_SYNC
Operation Type: Synchronous
Alter the Operation as shown

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

100

Routings Tab

Click on the routing name created (in this case: ~IMPORTED~22335)

Click on the Connector Properties tab and set the properties as shown:

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

101

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: http://<Server>:<Port>/<client
specific>/CllReceiveAccountingFromPSFT/cllreceiveaccountingfrompsftebs
_client_ep

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.14.5 Queue Setup

Go To: Home > PeopleTools > Integration Broker > Integration Setup > Queue
Search for the Queue GP_POST_GL
Set the queue status to Run

Save.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

102

1.14.6 Batch Publish Rules

Go To: Home > Enterprise Components > Integration Definitions > Batch Publish
Rules
Search for the Message GP_POST_GL
Configure as shown in the screen below.
Batch Publish Rules tab

Record Mapping tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

103

Batch Programs tab

Save.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

104

1.15 JobCode
To send the job code from PeopleSoft to EBS using WebServices, follow these steps:
Import BPEL WebService
Rename Imported Objects
Create publisher Peoplecode
Setup the Service Operation

1.15.1 Import BPEL WebService

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
Erro! A referncia de hiperlink no vlida. server>:<port>/<client specific path>/
cll_ReceiveJobsFromPSFT/cllreceivejobsfrompsftebs_client_ep?WSDL

Click Next
Select the Service to create (cllreceivejobsfrompsftebs_client_ep).

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

105

Click Next
Select the Services Operation do create.

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_JOBCODE_REQUEST
Response Message: CLLEBS_JOBCODE_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

106

Click Next
Select Use Existing Node and inform BPEL as the node

Click Finish.
A brief description of what was done is shown.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

107

1.15.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

Service: CLLRECEIVEJOBSFROMPSFTEBS_CLIE

New Name: CLLEBS_JOBCODE

Click on Rename

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

108

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_JOBCODE_SYNC

Click on Rename

The result should be: Operation Renamed

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

109

1.15.3 Service Operation CLLEBS_JOB_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_JOB
Service Operation: CLLEBS_JOB_SYNC
Operation Type: Synchronous
Alter the Operation as shown
Routings Tab

Click on the routing name created (in this case: ~IMPORTED~10117)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

110

Click on the Connector Properties tab and set the properties as shown:

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: Erro! A referncia de hiperlink no vlida. Server>:<Port>/<client


specific>/ cll_ReceiveJobsFromPSFT/cllreceivejobsfrompsftebs_client_ep

Ps.: Set the Service Operation Security Options according to your


organization policies.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

111

1.16 Organization
To send the organizations from PeopleSoft to EBS using WebServices, follow these
steps:
Import BPEL WebService
Rename Imported Objects
Create publisher Peoplecode
Setup the Service Operation

1.16.1 Import BPEL WebService

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
http://<soa server>:<port>/<client specific path>/
cll_ReceiveOrganizationsFromPSFT/cllreceiveorganizationsfrompsftebs_client_ep?
WSDL

Click Next
Select the Service to create (cllreceiveorganizationsfrompsftebs_client_ep).
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

112

Click Next
Select the Services Operation do create.

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_ORGANIZATION_REQUEST
Response Message: CLLEBS_ORGANIZATION_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

113

Click Next
Select Use Existing Node and inform BPEL as the node

Click Finish.
A brief description of what was done is shown.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

114

1.16.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

Service: CLLRECEIVEORGANIZATIONSFROMPSF

New Name: CLLEBS_ORGANIZATION

Click on Rename

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

115

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_ORGANIZATION_SYNC

Click on Rename

The result should be: Operation Renamed

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

116

1.16.3 Service Operation CLLEBS_ORGANIZATION_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_ORGANIZATION
Service Operation: CLLEBS_ORGANIZATION_SYNC
Operation Type: Synchronous
Alter the Operation as shown
Routings Tab

Click on the routing name created (in this case: ~IMPORTED~16792)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

117

Click on the Connector Properties tab and set the properties as shown:

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: http://<soa Server>:<Port>/<client specific>/


cll_ReceiveOrganizationsFromPSFT/cllreceiveorganizationsfrompsftebs_cli
ent_ep

Ps.: Set the Service Operation Security Options according to your


organization policies.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

118

1.17 Position
To send positions from PeopleSoft to EBS using WebServices, follow these steps:
Import BPEL WebService
Rename Imported Objects
Create publisher Peoplecode
Setup the Service Operation

1.17.1 Import BPEL WebService

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
http://<soa server>:<port>/<client specific
path>/cll_ReceivePositionsFromPSFT/cllreceivepositionsfrompsftebs_client_ep?WS
DL

Click Next
Select the Service to create (cllreceivepositionsfrompsftebs_client_ep).

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

119

Click Next
Select the Services Operation do create.

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_POSITION_REQUEST
Response Message: CLLEBS_POSITION_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

120

Click Next
Select Use Existing Node and inform BPEL as the node

Click Finish.
A brief description of what was done is shown.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

121

1.17.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

Service: CLLRECEIVEPOSITIONSFROMPSFTEBS

New Name: CLLEBS_POSITION

Click on Rename

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

122

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_POSITION_SYNC

Click on Rename

The result should be: Operation Renamed

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

123

1.17.3 Service Operation CLLEBS_POSITION_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_POSITION
Service Operation: CLLEBS_POSITION_SYNC
Operation Type: Synchronous
Alter the Operation as shown
Routings Tab

Click on the routing name created (in this case: ~IMPORTED~19414)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

124

Click on the Connector Properties tab and set the properties as shown:

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: http://<soa Server>:<Port>/<client


specific>/cll_ReceivePositionsFromPSFT/cllreceivepositionsfrompsftebs_clie
nt_ep

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

125

1.18 Bank and Branches


To create the bank and branches web services, follow these steps:
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation

1.18.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_BANKBRANCHES_REQUEST
Message Version: V1
Define the message as shown in the pictures

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

126

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

127

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/BankBranches"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/BankBranches"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Bank" type="BankType"/>
<xsd:complexType name="BankType">
<xsd:sequence>
<xsd:element name="BankCountryCode" type="xsd:string" minOccurs="0"/>
<xsd:element name="BankId" type="xsd:string" minOccurs="0"/>
<xsd:element name="Status" type="xsd:string" minOccurs="0"/>
<xsd:element name="BankName" type="xsd:date" minOccurs="0"/>
<xsd:element name="BankIdCode" type="xsd:string" minOccurs="0"/>
<xsd:element name="Country" type="xsd:string" minOccurs="0"/>
<xsd:element name="Address1" type="xsd:string" minOccurs="0"/>
<xsd:element name="Address2" type="xsd:string" minOccurs="0"/>
<xsd:element name="Address3" type="xsd:string" minOccurs="0"/>
<xsd:element name="Address4" type="xsd:string" minOccurs="0"/>
<xsd:element name="Num" type="xsd:string" minOccurs="0"/>
<xsd:element name="State" type="xsd:int" minOccurs="0"/>
<xsd:element name="City" type="xsd:string" minOccurs="0"/>
<xsd:element name="PostalCode" type="xsd:string" minOccurs="0"/>
<xsd:element name="Phone" type="xsd:string" minOccurs="0"/>
<xsd:element name="Branches" type="BranchCollection" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="BranchCollection">
<xsd:sequence>
<xsd:element name="Branch" type="Branch" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Branch">
<xsd:sequence>
<xsd:element name="BranchId" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchName" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchStatus" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchCountry" type="xsd:date" minOccurs="0"/>
<xsd:element name="BranchAddress1" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchAddress2" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchAddress3" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchAddress4" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchNum" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchState" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchCity" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchPostalCode" type="xsd:int" minOccurs="0"/>
<xsd:element name="BranchPhone" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchBankIdCode" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchCheckDigit" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchLocal" type="xsd:string" minOccurs="0"/>
<xsd:element name="BranchContactName" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Save.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

128

Add a new Message


Message Name: CLLEBS_BANKBRANCHES_RESPONSE
Message Version: V1
Define the message as shown in the pictures

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

129

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/BankBranches"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/BankBranches" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save

1.18.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_BANKBRANCHES
Define the service as shown

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

130

1.18.3 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_BANKBRANCHES
Service Operation: CLLEBS_BANKBRANCHES_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

Check the Active Flag


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

131

Check the routing action Generate Any-to-Local to add a routing accepting


request from anywhere.
Request Message: CLLEBS_BANKBRANCHES_REQUEST.V1
Response Message: CLLEBS_BANKBRANCHES_RESPONSE.V1
Handlers Tab

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

132

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your


organization policies.

1.18.4 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_BANKBRANCHES

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

133

Click the link Provide Web Service and follow the prints

Click Next

Click Next
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

134

Click Finish

1.19 Employee
To send employee from PeopleSoft to EBS using WebServices, follow these steps:
Import BPEL WebService
Rename Imported Objects
Create publisher Peoplecode
Setup the Service Operation

1.19.1 Import BPEL WebService

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

135

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
http://<soa server>:<port>/<client specific path>/
cll_ReceiveEmployeeFromPSFT/cllreceiveemployeefrompsftebs_client_ep?WSDL

Click Next
Select the Service to create (cllreceiveemployeefrompsftebs_client_ep).

Click Next
Select the Services Operation do create.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

136

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_EMPLOYEE_REQUEST
Response Message: CLLEBS_EMPLOYEE_RESPONSE

Click Next
Select Use Existing Node and inform BPEL as the node

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

137

Click Finish.
A brief description of what was done is shown.

1.19.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

LAD Add-on Localizations

Service: CLLRECEIVEEMPLOYEEFROMPSFTEBS_

New Name: CLLEBS_EMPLOYEE


EBS-PeopleSoft HCM Integration- Implementation Guide

138

Click on Rename

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_EMPLOYEE_SYNC

Click on Rename

The result should be: Operation Renamed

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

139

1.19.3 Service Operation CLLEBS_EMPLOYEE_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_EMPLOYEE_ACCT
Service Operation: CLLEBS_EMPLOYEE_SYNC
Operation Type: Synchronous
Alter the Operation as shown
Routings Tab

Click on the routing name created (in this case: ~IMPORTED~38519)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

140

Click on the Connector Properties tab and set the properties as shown:

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: http://<soa Server>:<Port>/<client specific>/


cll_ReceiveEmployeeFromPSFT/cllreceiveemployeefrompsftebs_client_ep

Ps.: Set the Service Operation Security Options according to your


organization policies.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

141

1.20 Employee Bank and Account


To send employee banks and accounts from PeopleSoft to EBS using WebServices,
follow these steps:
Import BPEL WebService
Rename Imported Objects
Create publisher Peoplecode
Setup the Service Operation

1.20.1 Import BPEL WebService

Go to: Home > PeopleTools > Integration Broker > Web Services > Consume Web
Service.
Follow the steps shown in the screenshots.
Select WSDL URL option and input the BPEL WSDL URL. It will look like this.
http://<soa server>:<port>/<client specific path>/
cll_ReceiveEmployeeBankAccountFromPSFT/cllreceiveemployeebankaccountfrom
psftebs_client_ep?WSDL

Click Next
Select the Service to create (cllreceiveemployeebankaccountfrompsftebs_client_ep).
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

142

Click Next
Select the Services Operation do create.

Click Next
For each service operation, inform the request / response messages to create.
In this case, inform for the:
Request Message: CLLEBS_EMPL_BANK_ACCT_REQUEST
Response Message: CLLEBS_EMPL_BANK_ACCT_RESPONSE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

143

Click Next
Select Use Existing Node and inform BPEL as the node

Click Finish.
A brief description of what was done is shown.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

144

1.20.2 Rename Imported Objects

Go To: Home > PeopleTools > Integration Broker > Service Utilities > Service
Administration
The following items will be renamed:

Service

Service Operation

Service
Click on tab Service and open the Rename section
Set the fields as:

Service: CLLRECEIVEEMPLOYEEBANKACCOUNTF

New Name: CLLEBS_EMPL_BANK_ACCT

Click on Rename

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

145

A confirmation screen pop up

The result should be: Service Renamed


Click on the tab Service Operations
Set the fields as:

Service Operation: PROCESS

New Name: CLLEBS_EMPL_BANK_ACCT_SYNC

Click on Rename

The result should be: Operation Renamed

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

146

1.20.3 Service Operation CLLEBS_EMPL_BANK_ACCT_SYNC

Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_EMPL_BANK_ACCT
Service Operation: CLLEBS_EMPL_BANK_ACCT_SYNC
Operation Type: Synchronous
Alter the Operation as shown
Routings Tab

Click on the routing name created (in this case: ~IMPORTED~11540)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

147

Click on the Connector Properties tab and set the properties as shown:

Content-Type: text/xml

sendUncompressed: Y

Method: POST

SOAPUpContent: Y

URL: http://<soa Server>:<Port>/<client specific>/


cll_ReceiveEmployeeBankAccountFromPSFT/cllreceiveemployeebankaccou
ntfrompsftebs_client_ep

Ps.: Set the Service Operation Security Options according to your


organization policies.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

148

1.21 SEFIP Autonomous


To create the SEFIP web services, follow these steps:
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.21.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_AUTON_SEFIP_REQUEST
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

149

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/AutonomousSefip"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/AutonomousSefip"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Sefip">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="END_YEAR" type="xsd:integer"/>
<xsd:element maxOccurs="1" minOccurs="1" name="START_MONTH" type="xsd:integer"/>
<xsd:element maxOccurs="1" minOccurs="1" name="INSCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="TAKE_INS_TYPE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="STAKER_INSCR" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="REG_NUMBER" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="SEFIP_CAT" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="PERS_NAME" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="CBO_CODE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="INS_DISC_VAL" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="MULTI_VINC" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="INSURED_DSC" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="BATCH_CODE" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="REFERENCE" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Save.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

150

Add a new Message


Message Name: CLLEBS_AUTON_SEFIP_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

151

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/psft/ebo/AutonomousSefip"
xmlns="http://xmlns.oracle.com/cll/psft/ebo/AutonomousSefip"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="Response">
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.

1.21.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_AUTON_SEFIP
Define the service as shown

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

152

1.21.3 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_AUTON_SEFIP
Service Operation: CLLEBS_AUTON_SEFIP_SYNC
Operation Type: Synchronous
Define the service operation as shown
General Tab

Check the Active Flag


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

153

Check the routing action Generate Any-to-Local to add a routing accepting


request from anywhere.
Request Message: CLLEBS_AUTON_SEFIP_REQUEST.V1
Response Message: CLLEBS_AUTON_SEFIP_RESPONSE.V1
Handlers Tab

Add a handler.
Handler Details:

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

154

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.

Ps.: Set the Service Operation Security Options according to your organization
policies.

1.21.4 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_AUTON_SEFIP

Click the link Provide Web Service and follow the prints

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

155

Click Next

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

156

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

157

1.22 Accounting Header


To create the Accounting Header web services, follow these steps:
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.22.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_ACCOUNTING_HDR_REQUEST
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

Schema Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

158

Message Schema:
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/F357/CllReceiveAccountingFromPSFT/CllReceivePayrollHeader
FromPSFTEBS" schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceivepayrollheaderfrompsftebs_client_ep?XSD
=xsd/CllReceivePayrollHeaderFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

Save.
Add a new Message
Message Name: CLLEBS_ACCOUNTING_HDR_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

159

Schema Tab

Message Schema:
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import
namespace="http://xmlns.oracle.com/F357/CllReceiveAccountingFromPSFT/CllReceivePayrollHeader
FromPSFTEBS" schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/cllreceivepayrollheaderfrompsftebs_client_ep?XSD
=xsd/CllReceivePayrollHeaderFromPSFTEBS.xsd"/>
<import namespace="http://xmlns.oracle.com/cll/xsd/ErrorElement"
schemaLocation="http://addonvm1.br.oracle.com:8001/soainfra/services/cll/CllReceiveAccountingFromPSFT/apps/cll/xsd/ErrorElement.xsd"/>
</schema>

Save.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

160

1.22.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_ACCOUNTING_HDR
Define the service as shown

1.22.3 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_ACCOUNTING_HDR
Service Operation: CLLEBS_ACCOUNTING_HDR_SYNC
Operation Type: Synchronous
Define the service operation as shown
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

161

General Tab

Check the Active Flag


Check the routing action Generate Any-to-Local to add a routing accepting
request from anywhere.
Request Message: CLLEBS_ACCOUNTING_HDR_REQUEST.V1
Response Message: CLLEBS_ACCOUNTING_HDR_RESPONSE.V1
Handlers Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

162

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.
Ps.: Set the Service Operation Security Options according to your organization
policies.

1.22.4 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_ACCOUNTING_HDR

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

163

Click the link Provide Web Service and follow the prints

Click Next

Click Next

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

164

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

165

1.23 Accounting Results


To create the Accounting Results web services, follow these steps:
Define the request and response message
Define the Service
Create the Handler Peoplecode
Define the Service Operation
Provide Web Service

1.23.1 Request and Response Message


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Messages
Add a New Message
Message Name: CLLEBS_GL_ACCTG_RESUL_REQUEST
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

166

Schema Tab

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="GLAccountingResult">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayrollId" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="1" name="StatusFlag" type="xsd:string"/>
<xsd:element minOccurs="0" name="ErrorText" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Save.
Add a new Message
Message Name: CLLEBS_GL_ACCTG_RESUL_RESPONSE
Message Version: V1
Define the message as shown in the pictures
Message Definition Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

167

Schema Tab

Message Schema:
<?xml version="1.0"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns="http://xmlns.oracle.com/cll/ebo/GLAccountingResult"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="StatusRequest" type="StatusRequest"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ErrorMessage" type="xsd:string"/>
</xsd:sequence>
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

168

</xsd:complexType>
</xsd:element>
<xsd:simpleType name="StatusRequest">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ERROR"/>
<xsd:enumeration value="OK"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Save.

1.23.2 Service
Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Add a New Service
Service Name: CLLEBS_GL_ACCOUNTING_RESULTS
Define the service as shown

1.23.3 Service Operation


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Operations
Add a New Service Operation
Service Name: CLLEBS_GL_ACCOUNTING_RESULTS
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

169

Service Operation: CLLEBS_GL_ACCTG_RESULTS_SYNC


Operation Type: Synchronous
Define the service operation as shown
General Tab

Check the Active Flag


Check the routing action Generate Any-to-Local to add a routing accepting
request from anywhere.
Request Message: CLLEBS_GL_ACCTG_RESUL_REQUEST.V1
Response Message: CLLEBS_GL_ACCTG_RESUL_RESPONSE.V1
Handlers Tab

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

170

Save the Service Operation.


Then check if the routing has been created.
Routings Tab

Check if
Routing Type is Synch
Sender node is ~~Any~~
Receiver Node is your local node (in this case PSFT_HR)
Direction is Inbound
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

171

Status is Active
The name will be generated by PeopleSoft and may differ, but will be something
similar to the one in the picture.
Ps.: Set the Service Operation Security Options according to your organization
policies.

1.23.4 Provide Web Service


Go to: Home > PeopleTools > Integration Broker > Integration Setup > Service
Search for the service: CLLEBS_GL_ACCOUNTING_RESULTS

Click the link Provide Web Service and follow the prints

Click Next

Click Next

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

172

Click Finish

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

173

1.24 GL Business Unit


To setup a new GL Business Unit thats going to be used in this integration,
there area few things that need to be done

Create a Portal Registry

Set Security

1.24.1 Create Portal Registry


Go to: Home > PeopleTools > Portal > Structure and Content
Select Set Up HRMS

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

174

Go to: Home > PeopleTools > Portal > Structure and Content
Select Foundation Tables

Select Organization

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

175

Click the link at the botton Add Content Reference Link


Browse to EMPLOYEE > Set Up HRMS > Product Related > Payroll for North
America > GL
Interface > Review GL Business Unit

Setup as shown below

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

176

Save.
Go Back to Home > PeopleTools > Portal > Structure and Content
Select Set Up HRMS

Go to: Home > PeopleTools > Portal > Structure and Content
Select Foundation Tables

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

177

Select Organization

Click the link at the botton Add Content Reference Link


Browse to EMPLOYEE > Set Up HRMS > Product Related > Payroll for
North America > GL Interface > Journal Generator Template

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

178

Setup as shown below

Save

1.24.2 Set Permission


Go To: Home > PeopleTools > Security > Permissions & Roles > Permission List
Setup those permission lists: HCCPHR9000, HCCPHR9100 e HCCPHR3000
Follow these steps:
Pages Tab
Add a new Line and set the field value to ADMINISTER_GL_INTERFACE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

179

Click on the link Edit Components.

Click on the link Edit Pages next to the component name


BUS_UNIT_TBL_GL.

Click on the button Select All.


Click on Ok.
Now Click on the link Edit Pages next to the component name
JRNLGEN_APPL_ID.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

180

Click on the button Select All.


Click on Ok, then Ok and then Save.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

181

1.25 Controlling Area


Allow the user to setup Controllig Areas. Its necessary to save the cost centers.
Update objects in the Application Designer
Set Security

1.25.1 Update Object in Application Designer


Open the Application Designer
Open a component

Component Name: HPYP_CA_COMP_CD

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

182

Open the component properties

Select the Use tab.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

183

Check the Add check box


Click Ok
Save.
Open a Page

Page Name: HPYP_CA_COMP_CD

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

184

Edit the Effective Date field properties

In the Use tab, uncheck the field Display Only

Do the same for the Status field.


Save.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

185

1.25.2 Set Permission


Go To: Home > PeopleTools > Security > Permissions & Roles > Permission List
Setup those permission lists: HCCPHR9000, HCCPHR9100 e HCCPHR3000
Follow these steps:
Pages Tab
Add a new Line and set the field value to HPIP_HCM_TO_GL_(GBL)

Click on the link Edit Components.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

186

Click on the link Edit Pages next to the component name


HPYP_CA_COMP_CD.

Click on the button Select All.


Click on Ok, then Ok and then Save.

1.25.3 Oracle PeopleSoft Setup


This section describes how to configure Oracle PeopleSoft for the EBS / Peoplesoft Integration.
1) GL Business Unit on PeopleSoft HCM
a. Disable the option General Ledger on the install table.
Go to: Setup HRMS -> Installation -> Installation Table -> Products

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

187

b. Set up new ID Set with the same code as the Ledger ID.
Go to: PeopleTools -> Utilities -> Administration -> TableSet ID ->
Add New Value

Important: The ID Set should have always 5positions. If necessary


fill with zeros on the left.

c. Set up GL Business Unit (BU GL)


Go to: Set Up HQRS -> Foundation Tables -> Review GL Business
Units -> Add New Value

Important: The BU GL should have the same code as the ID Set


created on the previous step. The Default ID Set should have also
the same code as the ID Set created on the previous step.
d. Set up Controlling Area
Go to: Set Up HRMS -> Common Definitions -> GL Integrations ->
Common GL Objects -> View Controlling Areas -> Add New
Value

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

188

The Controlling rea is a key information in the cost Center set


up, although it is not associated to a HR Business Unit or GL
Business Unit. It represents the sharing or segregation of the set
up. It does not have to have the same ID as the Ledger ID.
Important: This information is mandatory for the cost Center
integration.

e. Associate the HR Business Unit to the GL Business Unit.


Go to: Set Up HQRS -> Foundation Tables -> Organization ->
Business Unit -> Business Unit Reference

Associate the HR Business Unit to the GL Business Unit.


Remember that the GL Business Unit is the EBS Ledger ID.

f.

Associate the ID Set to the record control ( table set control) for
the group of Business Unit table.
Go to: PeopleTools -> Utilities -> Administration -> TableSet
Control

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

189

Locate the Record Group ID FS_05 and associate the Set Id of the
account set up.
For each HR business unit, identify wich ledeger Will be used.
This information is used for the account set up for the global
payroll element groups.

After the EBS GL setup is concluded, when na update or insert event occur
on the cost Center and account tables, a business evente Will be fired,
sending the data to Peoplesoft.
Accounts:
Go to: Set Up HRMS -> Common Definitions -> ChartField Configuration ->
ChartField Values -> Acconts

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

190

The SetId is the EBS GL Ledger.

Cost Center:
Set Up HRMS -> Common Definitions -> GL Integrations -> Common GL
Objects -> View Cost Centers

IF a Field in Oracle EBS is larger than the maximum size of the Field in
Peoplesoft, it will be truncated.

2) Global Payroll Set Up for GL posting.


a. Set up the journal template for each GL Business Unit.
Go to: Set Up HRMS -> Foundation Table -> Organization ->
Review journal template default -> Add New Value
The Set Id represents the ledger.
The Template ID should be always PTMPLT

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

191

Save.

b. Active the Publish Rule Definition GP_POST_GL and disable


create message header and create message trailer options.
Go to: Enterprise Components -> Integration Definitions-> Batch
Publish Rules
Message Name: GP_POST_GL

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

192

Save.

c. Define the chartfields that Will be used on the integration for each
Pay Entity of the Global Payroll
Go to: Set Up HRMS - > Product Related -> Global Payroll &
Absence Mgmt -> Integration -> ChartFields

To know more about chartfields, go to PeopleBooks: PeopleSoft


Enterprise Global Payroll 9.0 PeopleBook > Integrating with
PeopleSoft Enterprise General Ledger
In this example, we defined a variable element to get the cost
Center code associated to the employee on the cost Center field of
the HRMS department table.
To know more about variable elements used for account
classification, go to PeopleBooks: PeopleBooks > PeopleSoft
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

193

Enterprise Global Payroll 9.0 PeopleBook > Defining Calculation


Elements > Defining a Variable

d. Associate the department table to the GL cost center (it is not


mandatory IF your company uses other field for the employee
record).
Go to: Set Up HRMS - > Product Related -> Global Payroll &
Absence Mgmt -> Integration -> Chartfields For Cost Center
Associate the cost Center to the Pay Entities and HR Business
Units.

Include the records combination considering the chartfield


elements.

To know more about cost Center records associated to records


combination rules, go to PeopleBooks: PeopleSoft Enterprise
Global Payroll 9.0 PeopleBook > Integrating with PeopleSoft
EnterpriseOne General Ledger >Mapping Cost Centers and
Accounts

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

194

3) Generating Integration
The last step of the payroll processing is the closing of the period. It
happens after all payments were done and the finalize process already
processed.
It is only possible to generate the payroll gl posting for the calendaries
already finalized.
Go to: Global Payroll & Absence Mgmt -> Time and Labor / GL Costs ->
Send Costs to GL

Select Finalize and Run.


The option Finalize determines that the data will be sent to EBS GL.
To know more about cost Center records associated to records
combination rules, go to PeopleBooks: PeopleBooks > PeopleSoft
Enterprise Global Payroll 9.0 PeopleBook > Integrating with PeopleSoft
Enterprise General Ledger

4) Checking the Results


After running the process, it is possible to check if there is any error or if it
was sucessfully processed for all account records.
Go to: Global Payroll & Absence Mgmt -> Time and Labor / GL Costs ->
Review Transaction Status

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

195

Transaction Status

It is possible to Access the Integration Broker data, IF the corresponding


user has the permition.

IF there is any error when sending the data to EBS GL Interface, the
process Will be cancelled and the accounting lot will be deleted from the
EBS GL Interface table.

5) Resending Data to GL
To resend data to GL it is necessay to reset the GL process.
Navegao: Global Payroll & Absence Mgmt -> Time and Labor / GL
Costs -> Reset GL
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

196

Select the calendar and Run.


After the conclusion of this process, the calendar will be available for the
Send Cost to GL process.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

197

CHAPTER

Configuring Oracle E-Business Suite

1.26 Setting Up Integration: EBS-PeopleSoft HCM Integration

This section describes how to configure Oracle E-Business Suite for the EBS-PeopleSoft HCM
Integration.

1.26.1 Setting Up GL Ledger to PSFT

Choose the Responsibility: CLL: EBS-PSFT Integration


> Setup > GL Ledger to PSFT
The GL Integration Parameter Form contain attributes used for Set of Books
association between Oracle EBS GL and Peoplesoft

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

198

This Form allows only Update and Insert data manipulation.


Fields:

Name

Description

Oracle Ledger

Should chosse the primary ledger already


configured in EBS that will be associated to
Peoplesoft Set ID.

Ledger Name

Description of the Primary Ledger.

Journal Category

Should select the Journal Category from the list of


values available.

Journal Source

Should select the Journal Category from the list of


values available.

Conversion Rate Type

Conversion rate type for EBS Ledger

PeopleSoft Set Id

Should fill with the Peoplesoft Set ID

PeopleSoft BUGL

Should fill with the Peoplesoft Set BUGL

SEGMENT1 a SEGMENT30

Oracle EBS Segment

Segment Description

Shows the Segment Description according to the


configuration done for the GL code combinations.

Fixed Value

Should fill with Y or N. Used when a fixed value


is defined for the corresponding segment.

PeopleSoft Segment

It Will be available only if the correspondent


Oracle EBS Segment is also in place.
Should fill with the Peoplesoft corresponding
Segment value.
Values allowed:
1) If the Fixed Value flag is Y, any value is
allowed.
2) If the Fixed Value flag is N, values
allowed are:
PIN_CHART1_VAL
PIN_CHART2_VAL
PIN_CHART3_VAL
PIN_CHART4_VAL
PIN_CHART5_VAL
PIN_CHART6_VAL
PIN_CHART7_VAL
PIN_CHART8_VAL

1.26.2 Setting Up HRMS Parameter to PSFT

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

199

Choose the Responsibility: CLL: EBS-PSFT Integration


-> Setup -> HRMS Parameters to PSFT
The HR Integration Parameter form contains attributes used for Business Group
association between Oracle EBS HRMS and PeopleSoft HCM.
Entity Type
There are five differents Entity Types:

Employee

Bank

Job

Position

Organization

Each entity type has its own attributes and has to be set up according to definitions
below.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

200

Entity Type: EMPLOYEE


Employees created on PeopleSoft will be sent to the corresponding EBS Business
Group defined on the parameter form, according to the PeopleSoft BU.
The Peoplesoft segment definition for the type Employee will be used to find the
corresponding GL code combination. This code combination and the ledger are
associated to the employee assignment on the screen Purchase Order
Information.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

201

Entity Type: BANK


Employee banks created on PeopleSoft will be sent to the corresponding EBS
Business Group defined on the parameter form, according to the PeopleSoft BU.
The Business Group definition should be the same as the definition used for the
type Employee.
The PeopleSoft segments for the type BANK will be used for the association with
the Bank Key Flexfield.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

202

Entity Type: JOB


Jobs created on PeopleSoft will be sent to the corresponding EBS business group
defined on the parameter form, according to the PeopleSoft Set Id. The PeopleSoft
segments for the type JOB will be used for the association with the Job Key
Flexfield.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

203

Entity Type: POSITION


Positions created on PeopleSoft will be sent to the corresponding EBS Business
Group defined on the parameter form, according to the PeopleSoft BU. The
PeopleSoft segments for the type POSITION will be used for the association with
the Position Key Flexfield.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

204

Entity Type: ORGANIZATION


Organizations created on PeopleSoft will be sent to the corresponding EBS Business
Group defined on the parameter form, according to the PeopleSoft Set Id. The
PeopleSoft segments for the type ORGANIZATION will not be used.

Fields:
Name

Description

Oracle Business Group

Should choose the Oracle Business Group


already configured in EBS that will be
associated to the PeopleSoft Set ID or
PeopleSoft BU

Business Group Name

Business Group Description

Job Group

Job Group used for the entity type Job

Entity Type

Entity Type: Employee, Bank, Job,


Position or Organization

PeopleSoft Set Id

Should fill the PeopleSoft Set Id depending on


the Entity Type

PeopleSoft BU

Should fill the PeopleSoft BU depending on the


Entity Type.

SEGMENT1 a SEGMENT30
LAD Add-on Localizations

Key Flex Field Segments, automatically

EBS-PeopleSoft HCM Integration- Implementation Guide

205

populated according to the Entity Type.


Segment Description

Description of the Key Flex Field Segment

Fixed Value

Should be filled when defining a fixed value for


the segment.

PeopleSoft Segment

Should be filled with a fixed value if the Fixed


Flag value = Y or filled with the EBO value
available on the list of values according to the
Entity Type.

1.26.3 Setting Up Establishment Parameters

Choose the Responsibility: CLL: EBS-PSFT Integration


> Setup > Establishment Parameters to PSFT
That setup define a EBS establishment related to PeopleSoft Establishment.

1.26.4 Setting Up Lookup Codes

Choose the Responsibility: Application Developer > Application > Lookups >
Common
Find the lookup type: NATIONALITY
Create a code: BRA
Meaning: Brazil

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

206

Find the lookup type: ADDRESS_TYPE


Create a code: H
Meaning: Home
Description: Home

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

207

1.26.5 Setting Up Payroll Definition

The LAD Add-On Localizations: EBS-PeopleSoft HCM Integration uses a default


payroll:
Choose the Responsibility: UK HRMS Manager > Payroll > Description
Name: CLL F357 Integration EBS Fin x PeopleSoft HCM
First Period End Date: 31-JAN-1951
This payroll must be configured in the system.
1.27 Setting Up: Oracle E-Business Suite Supplier Sites Extensions

Please follow the instructions below for personalizing this page:


NOTE: If you do not see a Personalize Page option then it is necessary to
setup two profile options as follows:

1. Navigation: System Administrator > Profile > System


FND: Personalization Region Link Enabled = Y
Personalize Self-Service Defn = Y
If you set up the profiles and the "Personalize" option does not appear on
pages then it will be necessary to perform a "bounce" in the Apache.

2. Profile Definition for Enable Extension for EBS-PST Integration


Navigation: Profile > System
Choose the profile: CLL_F357: Enable Extension for EBS-PST Integration
Assign value Yes to the profile.

3. Open the Enter Supplier page


Navigation: Payables > Suppliers > Entry
Search for a Supplier then press Update button ;

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

208

Open the Address Book page;

Press update button at the supplier address;

Press the Personalize Page in the page upper right corner.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

209

Look for Page Button Bar: (PageButtonBarRN) and press the Create Item
button

Important: If you have a button CLL Additional Info, skip this setup.

After opening Personalization page, define following information:

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

210

Level: Site
Item Style: Button
ID: CLL_F357_IN_USE
Destination URI:
OA.jsp?page=/oracle/apps/cll/lxm/webui/ExtensionUsagesPG&pExtendedPag
e=/oracle/apps/pos/supplier/webui/ByrAddrPG&&retainAM=Y&pExtendedT
able=AP_SUPPLIER_SITES_ALL&pConnectString=VENDOR_SITE_ID={@Ve
ndorSiteId}
Prompt: CLL Additional Info
View Instance: ByrSuppAM.SitesVO

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

211

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

212

1.27.1 Monitoring Payroll Interface from PSFT

Choose the Responsibility: CLL: EBS-PSFT Integration


> GL Interface > Monitor Payroll Interface from PSFT
That window show us the situation of the Payroll Interface fired from PSFT with
destiny Oracle EBS General Ledgers

Query Find Window

Monitoring the Payroll Interface

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

213

Ocurrences of the processing

1.27.2 Concurrents

Choose the Responsibility: CLL: EBS-PSFT Integration


-> Requests -> Run

Synchronize Account/Cost Center to PeopleSoft: This concurrent send


account and cost center values to PeopleSoft

Synchronize Company to PeopleSoft: This concurrent create a polling table


and synchronize the information to PeopleSoft.

Synchronize Establishment to PeopleSoft: This concurrent create a polling


table and synchronize the information to PeopleSoft.

Synchronize Bank/Branches to PeopleSoft: This concurrent create a polling


table and synchronize the information to PeopleSoft.

Integration Log Report: This concurrent create a report about BPEL flows.

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

214

1.27.3 Concurrents Sets


Choose the Responsibility: CLL: EBS-PSFT Integration
-> Requests -> Run -> Request Set
Loading PSFT Payroll data into Accounting GL: This concurrent request set
will validate the data and loading this data on General Ledgers.

1.27.4 Lookups

1.27.5 CLL_F357_HR_ADDRESS_TYPE

LAD Add-on Localizations

Code

Meaning

Tag

BILL

Billing

CO

BUSN

Business

CO

CAMP

Campus

CO

CHK

Check

CO

DORM

Dormitory

CO

HOME

Home

LEGL

Legal

CO

MAIL

Mailing

CO

OTH

Other

CO

OTH2

Other 2

CO

PERM

Permanent

CO

PREF

Preferred

CO

VTRN

Billing

CO

EBS-PeopleSoft HCM Integration- Implementation Guide

215

1.27.6 CLL_F357_HR_ENTITY_TYPE

Code

Meaning

TAG

BANK

BANK

BANK

EMPLOYEE

EMPLOYEE

PERSON

JOB

JOB

JOB

ORGANIZATION

ORGANIZATION

ORG

POSITION

POSITION

POSITION

Code

Meaning

TAG

Female

Male

Unknown

Code

Meaning

TAG

Civil Partnership

Common-Law

DP

Dissolved Civil Partnership

DP

Divorced

Head of Household

REG_PART

Married

Separated

Single

Surviving Civil Partner

Unknown

1.27.7 CLL_F357_HR_GENDER

1.27.8 CLL_F357_HR_MARITAL_STATUS

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

216

Widowed

Code

Meaning

TAG

21

Argentinian

ARG

31

Belgian

31

22

Bolivian

22

10

Brazilian

BRA

20

Brazilian Naturalize

BRAN

32

British

32

34

Canadian

34

23

Chilean

23

42

Chinese

42

37

French

37

30

German

30

39

Italian

39

41

Japanese

41

43

Korean

43

36

North-American

AM

50

Other

50

49

Other Asians

49

48

Other Latin-American

48

24

Paraguayan

24

45

Portuguese

PQH_PT

35

Spanish

35

38

Swiss

PQH_SE

25

Uruguayan

25

1.27.9 CLL_F357_HR_NATIONALITY

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

217

1.27.10 CLL_F357_HR_PERSON_TYPE

Code

Meaning

TAG

CWR

Contingent Worker

Student

EMP

Employee

Employee

Code

Meaning

TAG

BUSN

Business

W1

CAMP

Campus

W1

DORM

Dormitory

W1

FAX

FAX

W1

HOME

Home

H1

MAIN

Main

W1

CELL

Mobile

W1

OTR

Other

W1

PGR1

Pager 1

W1

PGR2

Pager 2

W1

TELX

Telex

W1

WORK

Work

W1

1.27.11 CLL_F357_HR_PHONE_TYPE

1.27.12 CLL_F357_PSFT_BANK

LAD Add-on Localizations

Code

Meaning

ACCOUNT

BankAcctAccount

BANK

BankAcctBank

EBS-PeopleSoft HCM Integration- Implementation Guide

218

BRANCH

BankAcctBranch

COUNTRY

BankAcctCountry

1.27.13 CLL_F357_PSFT_COA
Code

Meaning

ACCOUNT

Account

PIN_CHART1_VAL

Chart of Accounts 1

PIN_CHART2_VAL

Chart of Accounts 2

PIN_CHART3_VAL

Chart of Accounts 3

PIN_CHART4_VAL

Chart of Accounts 4

PIN_CHART5_VAL

Chart of Accounts 5

PIN_CHART6_VAL

Chart of Accounts 6

PIN_CHART7_VAL

Chart of Accounts 7

PIN_CHART8_VAL

Chart of Accounts 8

1.27.14 CLL_F357_PSFT_EMPLOYEE
Code

Meaning

ACCOUNT

JobAccount

COSTCENTER

JobCostCenter

DEPARTMENT

JobDeptId

ESTABLISHMENT

JobEstablismentId

1.27.15 CLL_F357_PSFT_JOB

LAD Add-on Localizations

Code

Meaning

JOBCODE

JobCode

DESCR

JobTitle

EBS-PeopleSoft HCM Integration- Implementation Guide

219

1.27.16 CLL_F357_PSFT_POSITION
Code

Meaning

POSITION_NBR

PosCode

DESCR

PosTitle

1.27.17 CLL_F357_GL_ACCT_HEADER_STATUS
Code

Meaning

Cancelled

Error

ER

Reversal Error

Fully Filled

In-Transit

Posted to GL

Request for Reversal

RV

Reverted

Undefined

Validated

1.27.18 CLL_F357_PSFT_LANGUAGES

LAD Add-on Localizations

Code

Meaning

ESA

LATIN AMERICAN SPANISH

PTB

BRAZILIAN PORTUGUESE

US

AMERICAN

EBS-PeopleSoft HCM Integration- Implementation Guide

220

1.27.19 Hook GL Extensions

EBS-PeopleSoft HCM Integration provides templates packages that you use as the
basis of your extension.
Print out and review the following files before you begin writing transaction
costing extensions. The files are located in the CLL_TOP/patch/115/sql directory.

CLLEPPRS.pls References Extension Package Specification Template. If you


create functions within the package, outside the predefined procedure, you must
also modify this package.

CLLEPPRB.pls - References Extension Package Body Template. This file


contains the function that you modify to implement transaction cost ex-tensions.
You can define as many functions as you like within this package or within the
pre-defined function.

Tip: After you write the function, do not forget to compile it and store it in the
database.

Procedure Accounts
The following table lists the parameters for accounts extensions.

LAD Add-on Localizations

Parameter Usage

Usage

Type

Description

p_ebs_account

IN

VARCHAR2

EBS account value

p_dest_account

OUT

VARCHAR2

PSFT account value

p_ebs_chart_acct_id

IN

VARCHAR2

Chart of account identifier

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

EBS-PeopleSoft HCM Integration- Implementation Guide

221

Procedure Cost_Center
The following table lists the parameters for cost center extensions.
Parameter Usage

Usage

Type

Description

p_ebs_cost_center

IN

VARCHAR2

EBS cost center value

p_dest_cost_center

OUT

VARCHAR2

PSFTcost center value

p_ebs_chart_acct_id

IN

VARCHAR2

Chart of account identifier

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

Procedure Company
The following table lists the parameters for company extensions.
Parameter Usage

Usage

Type

Description

p_ebs_company

IN

VARCHAR2

EBS company value

p_dest_company

OUT

VARCHAR2

PSFT company value

p_ledger_id

IN

VARCHAR2

Ledger identifier

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

1.27.20 Hook HR Extensions

EBS-PeopleSoft HCM Integration provides templates packages that you use as the
basis of your extension.
Print out and review the following files before you begin writing transaction
costing extensions. The files are located in the CLL_TOP/patch/115/sql directory.

CLLEPHRS.pls HR Extension Package Specification Template. If you create


functions within the package, outside the predefined procedure, you must also
modify this package.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

222

CLLEPHRB.pls - HR Extension Package Body Template. This file contains the


function that you modify to implement transaction cost ex-tensions. You can
define as many functions as you like within this package or within the pre-defined
function.

Tip: After you write the function, do not forget to compile it and store it in the
database.

Procedure Job
The following table lists the parameters for job extensions.
Parameter Usage

Usage

Type

Description

p_ebs_business_group_id

IN

NUMBER

Business group identifier

p_dest_job

IN

VARCHAR2

PSFT job value

p_ebs_job

IN

VARCHAR2

EBS job falue

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

Procedure Organization
The following table lists the parameters for organization extensions.

LAD Add-on Localizations

Parameter Usage

Usage

Type

Description

p_ebs_business_group_id

IN

NUMBER

Business group identifier

p_dest_organization

IN

VARCHAR2

PSFT organization value

p_ebs_organization

IN

VARCHAR2

EBS organization value

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

EBS-PeopleSoft HCM Integration- Implementation Guide

223

Procedure Position
The following table lists the parameters for position extensions.

LAD Add-on Localizations

Parameter Usage

Usage

Type

Description

p_ebs_business_group_id

IN

NUMBER

Business group identifier

p_dest_position

IN

VARCHAR2

PSFT position value

p_ebs_position

IN

VARCHAR2

EBS position

p_return_code

OUT

VARCHAR2

Error code

p_return_message

OUT

VARCHAR2

Error message

EBS-PeopleSoft HCM Integration- Implementation Guide

224

CHAPTER

Table Definition

Table Definition

The Table Definition section contains a detailed definition of each table for
that Integration. For each table, the following information are available:
objective, column description, primary key, unique key, check constraints,
foreign key, indexes, quick codes and sequences.

CLL_F357_ACCT_CC_POLLING
The following chart describes the Account and Cost Center Polling Table
populated by the concurrent Synchronize Account/Cost Center to
PeopleSoft. Every time there is an update on existing data or a new record is
created for Account or Cost Center on Oracle E-Business Suite, the concurrent
will populate this table with the corresponding changed data and set the field
process_flag to N.

Column

Null / Not Null

Type of Data

Description

LEDGER_ID

NOT NULL

VARCHAR2(5)

PeopleSoft SetId Identifier

CHART_OF_ACCOUNTS_ID

NOT NULL

NUMBER (15)

Key flexfield structure defining column

FLEX_VALUE_ID

NOT NULL

NUMBER (15)

Flexfield segment value identifier

FLEX_VALUE

NOT NULL

VARCHAR2(150)

Flexfield segment value

VARCHAR2(150)

Flexfield segment value meaning

XML_TYPE

The XML with languages of accounts and

FLEX_VALUE_MEANING
XML_LANGUAGE

NOT NULL

cost centers
SEGMENT_ATTRIBUTE_TYPE

VARCHAR2(30)

Type: ACCOUNT or COSTCENTER

START_DATE_ACTIVE

DATE

Start Date

END_DATE_ACTIVE

DATE

End Date

LAST_UPDATE_DATE

NOT NULL

DATE

Last Update Date

ENABLED_FLAG

NOT NULL

VARCHAR2(1)

Enable Flag

Primary Key
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

225

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

CLL_F357_ACCT_CC_POLLING_N1

NOT UNIQUE

Sequence

Name of the Column


LEDGER_ID

CLL_F357_ACCT_CC_POLLING_N1

NOT UNIQUE

CHART_OF_ACCOUNTS_ID

CLL_F357_ACCT_CC_POLLING_N1

NOT UNIQUE

FLEX_VALUE_ID

Quick Codes
Name

Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

226

CLL_F357_BANKS_POLLING

The following charts describe the Bank and Branches Polling Tables
populated by the concurrent Synchronize Bank/Branches to PeopleSoft.
Every time there is an update on existing data or a new record is created for
Bank/Branches on Oracle E-Business Suite, the concurrent will populate these
tables with the corresponding changed data and set the process_flag to N.
Column

Null / Not Null

Type of Data

Description

BANK_PARTY_ID

NOT NULL

NUMBER(15)

Party identifier

STATUS

NOT NULL

VARCHAR2(1)

Party status flag

BANK_NAME

NOT NULL

VARCHAR2(360)

Name of this party

BANK_NUMBER

VARCHAR2(30)

Stores bank number for banks and branch number for bank

HOME_COUNTRY

VARCHAR2(2)

Home Country

ADDRESS_LINE1

VARCHAR2(240)

First line of the Identifying address

ADDRESS_LINE2

VARCHAR2(240)

Second line of the Identifying address

ADDRESS_LINE3

VARCHAR2(240)

Third line of the Identifying address

ADDRESS_LINE4

VARCHAR2(240)

Fourth line of the Identifying address

CITY

VARCHAR2(60)

City of the Identifying address

STATE

VARCHAR2(60)

State of the Identifying address

PROVINCE

VARCHAR2(60)

Province of the Identifying address

ZIP

VARCHAR2(60)

Postal Code of the Identifying address

COUNTRY

VARCHAR2(60)

The country listed in the TERRITORY_CODE column of the

PHONE_NUMBER

VARCHAR2(64)

Phone Number

PROCESS_FLAG

VARCHAR2(1)

Process Flag

LAST_UPDATE_DATE

DATE

Standard who column

branches, primarily ABA number for US bank branches

FND_TERRITORY table for the Identifying address

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

227

Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_BANKS_POLL_U1

UNIQUE

BANK_PARTY_ID

Quick Codes
Name

Column

Sequences
Name

Column

CLL_F357_BANK_BRANCHES_POLLING
Column

Null / Not

Type of Data

Description

Null
BANK_PARTY_ID

NOT NULL

NUMBER(15)

Party identifier

BANK_STATUS

NOT NULL

VARCHAR2(1)

Party status flag

BANK_NAME

NOT NULL

VARCHAR2(360)

Name of this party

VARCHAR2(30)

Stores bank number for banks and branch number

BANK_NUMBER

for bank branches, primarily ABA number for US


bank branches
HOME_COUNTRY

VARCHAR2(2)

Bank Country

BANK_ADDRESS_LINE1

VARCHAR2(240)

First line of the Identifying address

BANK_ADDRESS_LINE2

VARCHAR2(240)

Second line of the Identifying address

BANK_ADDRESS_LINE3

VARCHAR2(240)

Third line of the Identifying address

BANK_ADDRESS_LINE4

VARCHAR2(240)

Fourth line of the Identifying address

BANK_CITY

VARCHAR2(60)

City of the Identifying address

BANK_STATE

VARCHAR2(60)

State of the Identifying address

BANK_PROVINCE

VARCHAR2(60)

Province of the Identifying address

BANK_ZIP

VARCHAR2(60)

Postal Code of the Identifying address

BANK_COUNTRY

VARCHAR2(60)

The country listed in the TERRITORY_CODE


column of the FND_TERRITORY table for the
Identifying address

BANK_PHONE_NUMBER
BRANCH_PARTY_ID

VARCHAR2(64)
NOT NULL

BRANCH_STATUS

NUMBER(15,0)
VARCHAR2(1)

BANK_BRANCH_NAME

NOT NULL

VARCHAR2(360)

BANK_BRANCH_NAME_ALT

VARCHAR2(320)

BRANCH_NUMBER

VARCHAR2(30)

BRANCH_CHECK_DIGIT
START_DATE
END_DATE

LAD Add-on Localizations

Representation of organization name

VARCHAR2(150)
NOT NULL

DATE

Start Date

DATE

End Date

EBS-PeopleSoft HCM Integration- Implementation Guide

228

BRANCH_ADDRESS_LINE1

VARCHAR2(240)

First line of the Identifying address

BRANCH_ADDRESS_LINE2

VARCHAR2(240)

Second line of the Identifying address

BRANCH_ADDRESS_LINE3

VARCHAR2(240)

Third line of the Identifying address

BRANCH_ADDRESS_LINE4

VARCHAR2(240)

Fourth line of the Identifying address

BRANCH_CITY

VARCHAR2(60)

City of the Identifying address

BRANCH_STATE

VARCHAR2(60)

State of the Identifying address

BRANCH_PROVINCE

VARCHAR2(60)

Province of the Identifying address

BRANCH_ZIP

VARCHAR2(60)

Postal Code of the Identifying address

BRANCH_COUNTRY

VARCHAR2(60)

The country listed in the TERRITORY_CODE


column of the FND_TERRITORY table for the
Identifying address

BANK_INSTITUTION_TYPE

NOT NULL

VARCHAR2(30)

Institution Type

BANK_BRANCH_TYPE

VARCHAR2(30)

Bank Branch Type

DESCRIPTION

VARCHAR2(2000)

Corporate charter of organization

EFT_SWIFT_CODE

VARCHAR2(30)

EFT Swift Code

EFT_USER_NUMBER

VARCHAR2(30)

The number that identifier you as a user of


electronic funds transfer service to your bank or
clearing organization

EDI_ID_NUMBER

VARCHAR2(30)

EDI trading partner number for the supplier site

BANK_HOME_COUNTRY

VARCHAR2(2)

Bank Country

LAST_UPDATE_DATE

DATE

Standard who column

PROCESS_FLAG

VARCHAR2(1)

Process Flag

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

CLL_F357_BANK_BRANCHES_POLL_U1

UNIQUE

LAD Add-on Localizations

Sequence

Name of the Column

BANK_PARTY_ID

BRANCH_PARTY_ID

EBS-PeopleSoft HCM Integration- Implementation Guide

229

Quick Codes
Name

Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

230

CLL_F357_GL_PARAMETERS
The following table store a setup for integration points related a ledgers and
accounting for systems E-Business Suite and PeopleSoft
Column

Null / Not Null

Type of Data

Description

PARAM_ID

NOT NULL

NUMBER

GL Parameter identifier

LEDGER_ID

NOT NULL

NUMBER(15)

Ledger defining column

USER_JE_CATEGORY_NAME

NOT NULL

VARCHAR2(25)

Journal entry category user defined name

USER_JE_SOURCE_NAME

NOT NULL

VARCHAR2(25)

Journal entry source user defined name

PSOFT_SET_ID

VARCHAR2(5)

Peoplesoft Set ID

PSOFT_BUGL

VARCHAR2(5)

Peoplesoft Set BUGL

PSOFT_SEGM1

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE1

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM2

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE2

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM3

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE3

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM4

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE4

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM5

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE5

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM6

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE6

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM7

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE7

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM8

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE8

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM9

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE9

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM10

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE10

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM11

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE11

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM12

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE12

VARCHAR2(1)

Fixed value identifier (Yes or No)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

231

PSOFT_SEGM13

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE13

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM14

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE14

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM15

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE15

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM16

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE16

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM17

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE17

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM18

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE18

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM19

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE19

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM20

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE20

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM21

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE21

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM22

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE22

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM23

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE23

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM24

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE24

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM25

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE25

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM26

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE26

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM27

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE27

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM28

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE28

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM29

VARCHAR2(30)

PeopleSoft Segment

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

232

FIXED_VALUE29

VARCHAR2(1)

Fixed value identifier (Yes or No)

PSOFT_SEGM30

VARCHAR2(30)

PeopleSoft Segment

FIXED_VALUE30

VARCHAR2(1)

Fixed value identifier (Yes or No)

CREATION_DATE

NOT NULL

DATE

Standard who column

CREATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NUMBER

Standard who column

LAST_UPDATE_LOGIN

NUMBER

Standard who column

REQUEST_ID

NUMBER

Standard who column

PROGRAM_APPLICATION_ID

NUMBER

Standard who column

PROGRAM_ID

NUMBER

Standard who column

PROGRAM_UPDATE_DATE

DATE

Standard who column

VARCHAR2(30)

Identified

CONVERSION_RATE_TYPE

conversion

rate

type

to

currency code of Ledger

Primary Key
Name

Column

CLL_F357_GL_PARAMETERS_PK

PARAM_ID

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_GL_PARAMETERS_N1

NON UNIQUE

LEDGER_ID

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

233

NON UNIQUE

PSOFT_SET_ID

NON UNIQUE

PSOFT_BUGL

Quick Codes
Name

Column

Sequences
Name

Column

CLL_F357_GL_PARAMETERS_S

PARAM_ID

CLL_F357_HR_PARAMETERS

The following table store a setup for integration points related a Employee for
systems E-Business Suite and PeopleSoft.
Column

Null / Not Null

Type of Data

Description

PARAM_ID

NOT NULL

NUMBER

HRMS Parameter identifier

BUSINESS_GROUP_ID

NOT NULL

NUMBER

Business Group identifier

NUMBER

Job Group identifier

VARCHAR2(20)

Entity type

PSOFT_BUGL

VARCHAR2(20)

Peoplesoft Set ID

PSOFT_SET_ID

VARCHAR2(30)

Peoplesoft Set BUGL

PSOFT_SEGM1

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM2

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM3

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM4

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM5

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM6

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM7

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM8

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM9

VARCHAR2(30)

PeopleSoft Segment

JOB_GROUP_ID
ENTITY_TYPE

LAD Add-on Localizations

NOT NULL

EBS-PeopleSoft HCM Integration- Implementation Guide

234

PSOFT_SEGM10

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM11

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM12

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM13

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM14

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM15

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM16

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM17

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM18

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM19

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM20

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM21

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM22

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM23

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM24

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM25

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM26

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM27

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM28

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM29

VARCHAR2(30)

PeopleSoft Segment

PSOFT_SEGM30

VARCHAR2(30)

PeopleSoft Segment

CREATION_DATE

NOT NULL

DATE

Standard who column

CREATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NUMBER

Standard who column

LAST_UPDATE_LOGIN

NUMBER

Standard who column

REQUEST_ID

NUMBER

Standard who column

PROGRAM_APPLICATION_ID

NUMBER

Standard who column

PROGRAM_ID

NUMBER

Standard who column

PROGRAM_UPDATE_DATE

DATE

Standard who column

FIXED_VALUE1

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE2

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE3

VARCHAR2(1)

Fixed value identifier (Yes or No)

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

235

FIXED_VALUE4

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE5

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE6

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE7

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE8

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE9

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE10

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE11

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE12

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE13

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE14

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE15

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE16

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE17

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE18

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE19

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE20

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE21

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE22

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE23

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE24

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE25

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE26

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE27

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE28

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE29

VARCHAR2(1)

Fixed value identifier (Yes or No)

FIXED_VALUE30

VARCHAR2(1)

Fixed value identifier (Yes or No)

LEDGER_ID

NUMBER

Ledger defining column

Primary Key
Name

Column

CLL_F357_GL_PARAMETERS_PK

PARAM_ID

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

236

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_HR_PARAMETERS_U1

UNIQUE

PARAM_ID

CLL_F357_HR_PARAMETERS_U2

NON UNIQUE

ENTITY_TYPE

NON UNIQUE

BUSINESS_GROUP_ID

NON UNIQUE

LEDGER_ID

Quick Codes
Name

Column

Sequences
Name

Column

CLL_F357_HR_PARAMETERS_S

PARAM_ID

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

237

CLL_F357_LE_COMPANY_POLLING
The following chart describes the Company Polling Table populated by the
concurrent Synchronize Company to PeopleSoft. Every time there is an
update on existing data or a new record is created for Company on Oracle EBusiness Suite, the concurrent will populate this table with the corresponding
changed data and set the field process_flag to N.

Column

Null / Not Null

Type of Data

Description

LEDGER_ID

NOT NULL

NUMBER(15)

Ledger Identification

LEGAL_ENTITY_ID

NOT NULL

NUMBER(15)

Legal Entity Identification

VARCHAR2(30)

Developer Flexfield Segment Context

LE_INFORMATION_CONTEXT
NAME

NOT NULL

VARCHAR2(240)

Name

PARTY_ID

NOT NULL

NUMBER(15)

Party Identification

LEGAL_ENTITY_IDENTIFIER

VARCHAR2(30)

Tax Payer ID or a dummy registration

ACTIVITY_CODE

VARCHAR2(150)

Activity Code

SUB_ACTIVITY_CODE

VARCHAR2(150)

Sub Activity Code

TYPE_OF_COMPANY

VARCHAR2(50)

Type of the Company

ACTIVITY_CATEGORY

VARCHAR2(60)

Activity Category

ACTIVITY_DESCRIPTION

VARCHAR2(80)

Activity Description

LE_EFFECTIVE_FROM

DATE

Legal Entity Start Date

LE_EFFECTIVE_TO

DATE

Legal Entity End Date

ATTRIBUTE_CATEGORY

VARCHAR2(30)

Descriptive Flexfield structure definition

ATTRIBUTE1

VARCHAR2(150)

Descriptive Flexfield segment 1

ATTRIBUTE2

VARCHAR2(150)

Descriptive Flexfield segment 2

ATTRIBUTE3

VARCHAR2(150)

Descriptive Flexfield segment 3

ATTRIBUTE4

VARCHAR2(150)

Descriptive Flexfield segment 4

ATTRIBUTE5

VARCHAR2(150)

Descriptive Flexfield segment 5

ATTRIBUTE6

VARCHAR2(150)

Descriptive Flexfield segment 6

ATTRIBUTE7

VARCHAR2(150)

Descriptive Flexfield segment 7

ATTRIBUTE8

VARCHAR2(150)

Descriptive Flexfield segment 8

ATTRIBUTE9

VARCHAR2(150)

Descriptive Flexfield segment 9

ATTRIBUTE10

VARCHAR2(150)

Descriptive Flexfield segment 10

ATTRIBUTE11

VARCHAR2(150)

Descriptive Flexfield segment 11

ATTRIBUTE12

VARCHAR2(150)

Descriptive Flexfield segment 12

ATTRIBUTE13

VARCHAR2(150)

Descriptive Flexfield segment 13

ATTRIBUTE14

VARCHAR2(150)

Descriptive Flexfield segment 14

ATTRIBUTE15

VARCHAR2(150)

Descriptive Flexfield segment 15

ATTRIBUTE16

VARCHAR2(150)

Descriptive Flexfield segment 16

ATTRIBUTE17

VARCHAR2(150)

Descriptive Flexfield segment 17

ATTRIBUTE18

VARCHAR2(150)

Descriptive Flexfield segment 18

ATTRIBUTE19

VARCHAR2(150)

Descriptive Flexfield segment 19

ATTRIBUTE20

VARCHAR2(150)

Descriptive Flexfield segment 20


Registration Number of the Identifying

number

REGISTRATION_NUMBER

NOT NULL

VARCHAR2(30)

LEGISLATIVE_CAT_CODE

NOT NULL

VARCHAR2(30)

Registration
Legislative Category Code of Identifying
Registration
EFFECTIVE_FROM

DATE

Start Date of Legal Entity Registration

EFFECTIVE_TO

DATE

LOCATION_ID

NUMBER(15)

Location Identifier

ADDRESS_STYLE

VARCHAR2(7)

Legal Address: Address Style used for

(Identifying)
End date of a Legal Entity Registration (
Identifying)

this formatting Address from

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

238

Region_2,Region_2,Region_3 etc.
ADDRESS_LINE_1

VARCHAR2(240)

Legal Address: Address Line 1

ADDRESS_LINE_2

VARCHAR2(240)

Legal Address: Address Line 2

ADDRESS_LINE_3

VARCHAR2(240)

Legal Address: Address Line 3

TOWN_OR_CITY

VARCHAR2(30)

Legal Address: Town or City

REGION_1

VARCHAR2(120)

Legal Address: Region 1

REGION_2

VARCHAR2(120)

Legal Address: Region 2

REGION_3

VARCHAR2(120)

Legal Address: Region 3

POSTAL_CODE

VARCHAR2(30)

Legal Address: Postal Code

COUNTRY

VARCHAR2(60)

Legal Address: Country

PROCESS_FLAG

VARCHAR2(1)

Process Flag

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_LE_COMPANY_POLLING_U1

UNIQUE

LEGAL_ENTITY_ID

Quick Codes
Name

Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

239

CLL_F357_LE_ESTAB_POLLING

The following charts describe the Establishment and Registration Polling


Tables populated by the concurrent Synchronize Establishment to
PeopleSoft. Every time there is an update on existing data or a new record is
created for Establishment on Oracle E-Business Suite, the concurrent will
populate these tables with the corresponding changed data and set the field
process_flag to N.

Column

Null / Not Null

Type of Data

Description

LEDGER_ID

NOT NULL

NUMBER(15)

Ledger Identifier

MAIN_ESTABLISHMENT_FL

NOT NULL

VARCHAR2(1)

Main Establishment_Flag

ESTABLISHMENT_ID

NOT NULL

NUMBER(15)

Establishment Identifier

ESTABLISHMENT_NAME

NOT NULL

VARCHAR2(240)

Establishment Name

LEGAL_ENTITY_ID

NUMBER(15)

Identifier of the Legal Entity that owns the

REGISTRATION_NUMBER

VARCHAR2(30)

AG

Establishment
Registration Number of the Identifying
Registration

associated

to

the

Establishment
LEGISLATIVE_CAT_CODE

VARCHAR2(30)

Legislative Category of the Registration

ADDRESS_LINE_1

NOT NULL

VARCHAR2(240)

Establishment Address: Address Line 1

ADDRESS_LINE_2

VARCHAR2(240)

Establishment Address: Address Line 2

ADDRESS_LINE_3

VARCHAR2(240)

Establishment Address: Address Line 3

TOWN_OR_CITY

VARCHAR2(30)

Establishment Address: Town Or City

REGION_1

VARCHAR2(120)

Establishment Address: Region 1

REGION_2

VARCHAR2(120)

Establishment Address: Region 2

REGION_3

VARCHAR2(120)

Establishment Address: Region 3

POSTAL_CODE

VARCHAR2(30)

Establishment Address: Postal Code

COUNTRY

VARCHAR2(60)

Establishment Address: Country

LOCATION_ID

NUMBER

Establishment Address: Location ID

ETB_EFFECTIVE_FROM

DATE

Effective From of the Establishment

ETB_EFFECTIVE_TO

DATE

Effective To of the Establishment

CHART_OF_ACCOUNTS_ID

NUMBER(15)

Chart Of Accounts Identifier

IBGE_CODE

VARCHAR2(360)

IBGE Code

PROCESS_FLAG

VARCHAR2(1)

Process Flag

LAST_UPDATE_DATE

DATE

Standard who column

Primary Key
Name

Column

Other Unique Keys


Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

240

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_LE_ESTAB_POLLING_U1

UNIQUE

ESTABLISHMENT_ID

Quick Codes
Name

Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

241

CLL_F357_LE_PARAMETERS

The following table store a setup for integration points related a


Establishment for systems E-Business Suite and PeopleSoft.

Column

Null / Not Null

Type of Data

Description

PARAM_ID

NOT NULL

NUMBER

Establishment parameter identifier

ESTABLISHMENT_ID

NOT NULL

NUMBER

EBS Establishment identifier

PSOFT_ESTABID

NOT NULL

VARCHAR2(12)

PeopleSoft establishment identifier

CREATED_BY

NOT NULL

NUMBER

Standard who column

CREATION_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

NUMBER

Standard who column

LAST_UPDATE_LOGIN

Primary Key
Name

Column

CLL_F357_LE_PARAMETERS_PK

PARAM_ID

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_LE_PARAMETERS_N1

UNIQUE

ESTABLISHMENT_ID

PSOFT_ESTABID

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

242

Quick Codes
Name

Column

Sequences
Name

Column

CLL_F357_LE_PARAMETERS_S

PARAM_ID

CLL_F357_LE_REGIST_POLLING

Column

Type of Data

Description

LEDGER_ID

Null / Not Null

NUMBER(15)

Ledger Identifier

MAIN_ESTABLISHMENT_FLAG

VARCHAR2(1)

Main Establishment_Flag

ESTABLISHMENT_ID

NUMBER(15)

Establishment Identifier

REGISTRATION_ID

NUMBER(15)

Registration Identifier

ESTABLISHMENT_NAME

VARCHAR2(240)

Establishment Name

LEGAL_ENTITY_ID

NUMBER(15)

Identifier of the Legal Entity that owns the

ETB_REGISTRATION_NUMBER

VARCHAR2(30)

LEGISLATIVE_CAT_CODE

VARCHAR2(30)

Legislative Category of the Registration

ADDRESS_LINE_1

VARCHAR2(240)

Establishment Address: Address Line 1

ADDRESS_LINE_2

VARCHAR2(240)

Establishment Address: Address Line 2

ADDRESS_LINE_3

VARCHAR2(240)

Establishment Address: Address Line 3

TOWN_OR_CITY

VARCHAR2(30)

Establishment Address: Town Or City

REGION_1

VARCHAR2(120)

Establishment Address: Region 1

REGION_2

VARCHAR2(120)

Establishment Address: Region 2

REGION_3

VARCHAR2(120)

Establishment Address: Region 3

POSTAL_CODE

VARCHAR2(30)

Establishment Address: Postal Code

COUNTRY

VARCHAR2(60)

Establishment Address: Country

LOCATION_ID

NUMBER

Establishment Address: Location ID

ETB_EFFECTIVE_FROM

DATE

Effective From of the Establishment

ETB_EFFECTIVE_TO

DATE

Effective To of the Establishment

CHART_OF_ACCOUNTS_ID

NUMBER(15)

Chart Of Accounts Identifier

REGISTRATION_NUMBER

VARCHAR2(30)

Registration Number of the Registration

REGISTRATION_CODE_LE

VARCHAR2(30)

Legal Entity Registration Code

NAME

VARCHAR2(240)

Jurisdiction Name

IBGE_CODE

VARCHAR2(360)

IBGE Code

PROCESS_FLAG

VARCHAR2(1)

Process Flag

Establishment
Registration Number of the Identifying
Registration associated to the Establishment

Primary Key
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

243

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_LE_REGIST_POLLING_U1

NOT UNIQUE

REGISTRATION_ID

CLL_F357_LE_REGIST_POLLING_U1

NOT UNIQUE

ESTABLISHMENT_ID

Quick Codes
Name

Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

244

CLL_F357_LOG

Column

Null / Not Null

Type of Data

Description

LOG_ID

NOT NULL

NUMBER

Log Identifier

INSTANCE_ID

NOT NULL

NUMBRE

Weblogic Instance Identifier

MESSAGE_TEXT

NOT NULL

VARCHAR2(4000)

Establishment Identifier

CREATION_DATE

NOT NULL

DATE

Standard who column

CREATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NUMBER

Standard who column

LAST_UPDATE_LOGIN

NUMBER

Standard who column

REQUEST_ID

NUMBER

Standard who column

PROGRAM_APPLICATION_ID

NUMBER

Standard who column

PROGRAM_ID

NUMBER

Standard who column

PROGRAM_UPDATE_DATE

DATE

Standard who column

Primary Key
Name

Column

CLL_F357_LOG_PK

LOG_ID

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_LOG_PK

NOT UNIQUE

REGISTRATION_ID

CLL_F357_LE_REGIST_POLLING_U1

NOT UNIQUE

ESTABLISHMENT_ID

Quick Codes
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

245

Sequences
Name

Column

CLL_F357_LOG_S

LOG_ID

CLL_F357_POLLING_CONTROL

Stores the last read date to get INSS invoices of the module EBS Brazilian
Integrated Receiving.
Column

Null / Not Null

Type of Data

Description

ENTITY_NAME

NOT NULL

VARCHAR2(50)

Identify polling name

DATE

Last read date to polling table

LAST_READ_DATE

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

246

Indexes
Name

Type

CLL_F357_POLLING_CONTROL_U1

UNIQUE

Sequence

Name of the Column

ENTITY_NAME

Sequences
Name

Column

CLL_F357_REFERENCES

Store all the target and destination values for each referecence type such as:

ACCOUNT

BANK

COST_CENTER

COMPANY

JOB

ORGANIZATION

POSITION

EMPLOYEE

ASSIGNMENT

Column

Null / Not Null

Type of Data

Description

REFERENCE_ID

NOT NULL

NUMBER

Reference identifier

SOURCE_REF_ID

NOT NULL

NUMBER

Source reference identifier

REFERENCE_TYPE

NOT NULL

VARCHAR2(30)

Reference type value

EBS_VALUE

VARCHAR2(240)

EBS value

DEST_VALUE

VARCHAR2(240)

Destination value

CREATED_BY

NOT NULL

NUMBER

Standard who column

CREATION_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATE_LOGIN

NUMBER

Standard who column

REQUEST_ID

NUMBER

Standard who column

PROGRAM_APPLICATION_ID

NUMB ER

Standard who column

PROGRAM_ID

NUMBER

Standard who column

PROGRAM_UPDATE_DATE

DATE

Standard who column

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

247

Primary Key
Name

Column

CLL_F357_REFERENCES_PK

REFERENCE_ID

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

CLL_F357_REFERENCES_U1

UNIQUE

Name of the Column


SOURCE_REF_ID
REFERENCE_TYPE
EBS_VALUE
DEST_VALUE

Quick Codes
Name

Column

Sequences
Name

Column

CLL_F357_REFERENCES_S

REFERENCE_ID

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

248

CLL_F357_SUPPLIER_SITES_EXT
Stores the additional information to the supplier sites.
Column

Null / Not Null

Type of Data

Description

VENDOR_SITE_ID

NOT NULL

NUMBER

Identify Vendor Site

ATTRIBUTE1

VARCHAR2(150)

PIS/PASEP Number

ATTRIBUTE2

VARCHAR2(150)

Worker Category

ATTRIBUTE3

VARCHAR2(150)

CBO Number

ATTRIBUTE4

VARCHAR2(150)

Descriptive Flexfield segment 4

ATTRIBUTE5

VARCHAR2(150)

Descriptive Flexfield segment 5

ATTRIBUTE6

VARCHAR2(150)

Descriptive Flexfield segment 6

ATTRIBUTE7

VARCHAR2(150)

Descriptive Flexfield segment 7

ATTRIBUTE8

VARCHAR2(150)

Descriptive Flexfield segment 8

ATTRIBUTE9

VARCHAR2(150)

Descriptive Flexfield segment 9

ATTRIBUTE10

VARCHAR2(150)

Descriptive Flexfield segment 10

ATTRIBUTE11

VARCHAR2(150)

Descriptive Flexfield segment 11

ATTRIBUTE12

VARCHAR2(150)

Descriptive Flexfield segment 12

ATTRIBUTE13

VARCHAR2(150)

Descriptive Flexfield segment 13

ATTRIBUTE14

VARCHAR2(150)

Descriptive Flexfield segment 14

ATTRIBUTE15

VARCHAR2(150)

Descriptive Flexfield segment 15

ATTRIBUTE_CATEGORY

VARCHAR2(30)

Descriptive Flexfield structure definition

CREATED_BY

NOT NULL

NUMBER

Standard who column

CREATION_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

NUMBER

Standard who column

LAST_UPDATE_LOGIN

Primary Key
Name

Column

Other Unique Keys


LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

249

Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_SUPPLIER_SITES_U1

UNIQUE

VENDOR_SITE_ID

Sequences
Name

Column

CLL_F357_GL_ACCOUNTING_HEADERS
Stores header information about the payroll from PSFT.
Column

Null / Not Null

Type of Data

Description

HEADER_ID

NOT NULL

NUMBER

Header identifier

PROCESS_INSTANCE_ID

NOT NULL

NUMBER

PSFT Payroll identifier

PAYROLL_ID

NOT NULL

VARCHAR2

PSFT Payroll identifier

PAYROLL_DATE

NOT NULL

DATE

Payroll date

BUSINESS_UNIT_GL

NOT NULL

VARCHAR2

PSFT Business Unit GL

STATUS_FLAG

NOT NULL

VARCHAR2

Status of the processing.

QUANTITY_LINES

NOT NULL

NUMBER

Number of records

CREDIT_AMOUNT

NOT NULL

NUMBER

Credit amount

DEBIT_AMOUNT

NOT NULL

NUMBER

Debit amount

GROUP_ID

NOT NULL

NUMBER

Group identifier

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

250

PREVIOUS_HEADER_ID

NUMBER

Previous header identifier

REQUEST_ID

NUMBER

Request id from Journal Import program


responsible to load data into GL.

CREATED_BY

NOT NULL

NUMBER

Standard who column

CREATION_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

NUMBER

Standard who column

LAST_UPDATE_LOGIN

Primary Key
Name

Column

CLL_F357_GL_ACCT_HDR_PK

HEADER_ID

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

Indexes
Name

Type

Sequence

Name of the Column

Sequences
Name

Column

CLL_F357_GL_ACCOUNTING_LINES
Stores all information about the processing of payroll data sended from PSFT.
LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

251

Column

Null / Not Null

Type of Data

Description

HEADER_ID

NOT NULL

NUMBER

Header identifier

PAYROLL_LINE_NUM

NOT NULL

NUMBER

Payroll Line Number

VARCHAR2

Line status

STATUS_FLAG
ACCOUNTING_DATE

NOT NULL

DATE

GL Accounting Date

CURRENCY_CODE

NOT NULL

VARCHAR2

Currency Code

DATE_CREATED

NOT NULL

DATE

Creation date of record

CREATED_BY

NOT NULL

NUMBER

Set who column

USER_JE_CATEGORY_NAME

NOT NULL

VARCHAR2

GL Categories

USER_JE_SOURCE_NAME

NOT NULL

VARCHAR2

GL Sources

ACTUAL_FLAG

NOT NULL

VARCHAR2

GL Actual status

LEDGER_ID

NOT NULL

NUMBER

GL Ledger id

SET_OF_BOOKS_ID

NUMBER

Set of books

CURRENCY_CONVERSION_DA

DATE

Conversion date of currency

VARCHAR2

Conversion type of currency

SEGMENT1

VARCHAR2

Accounting segment field

SEGMENT2

VARCHAR2

Accounting segment field

SEGMENT3

VARCHAR2

Accounting segment field

SEGMENT4

VARCHAR2

Accounting segment field

SEGMENT5

VARCHAR2

Accounting segment field

SEGMENT6

VARCHAR2

Accounting segment field

SEGMENT7

VARCHAR2

Accounting segment field

SEGMENT8

VARCHAR2

Accounting segment field

SEGMENT9

VARCHAR2

Accounting segment field

SEGMENT10

VARCHAR2

Accounting segment field

SEGMENT11

VARCHAR2

Accounting segment field

SEGMENT12

VARCHAR2

Accounting segment field

SEGMENT13

VARCHAR2

Accounting segment field

SEGMENT14

VARCHAR2

Accounting segment field

TE
USER_CURRENCY_CONVERSIO
N_TYPE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

252

SEGMENT15

VARCHAR2

Accounting segment field

SEGMENT16

VARCHAR2

Accounting segment field

SEGMENT17

VARCHAR2

Accounting segment field

SEGMENT18

VARCHAR2

Accounting segment field

SEGMENT19

VARCHAR2

Accounting segment field

SEGMENT20

VARCHAR2

Accounting segment field

SEGMENT21

VARCHAR2

Accounting segment field

SEGMENT22

VARCHAR2

Accounting segment field

SEGMENT23

VARCHAR2

Accounting segment field

SEGMENT24

VARCHAR2

Accounting segment field

SEGMENT25

VARCHAR2

Accounting segment field

SEGMENT26

VARCHAR2

Accounting segment field

SEGMENT27

VARCHAR2

Accounting segment field

SEGMENT28

VARCHAR2

Accounting segment field

SEGMENT29

VARCHAR2

Accounting segment field

SEGMENT30

VARCHAR2

Accounting segment field

ENTERED_DR

NUMBER

Entered credit amount

ENTERED_CR

NUMBER

Entered debit amount

TRANSACTION_DATE

DATE

GL Transaction date

REFERENCE1

VARCHAR2

Reference field

REFERENCE2

VARCHAR2

Reference field

REFERENCE3

VARCHAR2

Reference field

REFERENCE4

VARCHAR2

Reference field

REFERENCE5

VARCHAR2

Reference field

REFERENCE6

VARCHAR2

Reference field

REFERENCE7

VARCHAR2

Reference field

REFERENCE8

VARCHAR2

Reference field

REFERENCE9

VARCHAR2

Reference field

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

253

REFERENCE10

VARCHAR2

Reference field

REFERENCE11

VARCHAR2

Reference field

REFERENCE12

VARCHAR2

Reference field

REFERENCE13

VARCHAR2

Reference field

REFERENCE14

VARCHAR2

Reference field

REFERENCE15

VARCHAR2

Reference field

REFERENCE16

VARCHAR2

Reference field

REFERENCE17

VARCHAR2

Reference field

REFERENCE18

VARCHAR2

Reference field

REFERENCE19

VARCHAR2

Reference field

REFERENCE20

VARCHAR2

Reference field

REFERENCE21

VARCHAR2

Reference field

REFERENCE22

VARCHAR2

Reference field

REFERENCE23

VARCHAR2

Reference field

REFERENCE24

VARCHAR2

Reference field

REFERENCE25

VARCHAR2

Reference field

REFERENCE26

VARCHAR2

Reference field

REFERENCE27

VARCHAR2

Reference field

REFERENCE27

VARCHAR2

Reference field

REFERENCE28

VARCHAR2

Reference field

REFERENCE29

VARCHAR2

Reference field

REFERENCE30

NUMBER

Reference field

JE_BATCH_ID

VARCHAR2

PERIOD_NAME

NUMBER

GL Period name

JE_HEADER_ID

NUMBER

Header id

JE_LINE_NUM

NUMBER

Line num

CHART_OF_ACCOUNTS_ID

VARCHAR2

Chart of accounts

FUNCTIONAL_CURRENCY_CO

NUMBER

Functional currency code

DE

LAD Add-on Localizations

EBS-PeopleSoft HCM Integration- Implementation Guide

254

CODE_COMBINATION_ID

DATE

Code combinations ID

DATE_CREATED_IN_GL

CLOB

Creation date into GL

ERROR_DESCRIPTION

NUMBER

Error process description.

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

Column

CLL_F357_GL_ACCT_HDR_LIN_FK

HEADER_ID

Indexes
Name

Type

Sequence

Name of the Column

CLL_F357_GL_ACCT_LINES_U1

Unique

ASC

HEADER_ID

CLL_F357_GL_ACCT_LINES_U1

Unique

ASC

PARYOLL_LINE_NUM

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

255

CLL_F357_GL_ACCOUNTING_OCCURS
Stores information about the occurrence of the payroll processing on General
Ledgers.
Column

Null / Not Null

Type of Data

Description

HEADER_ID

NOT NULL

NUMBER

Header identifier

OCCURRENCE_NUM

NOT NULL

NUMBER

Sequence of occurrence processing

NEW_STATUS_FLAG

NOT NULL

VARCHAR2

New status

OLD_STATUS_FLAG

NOT NULL

VARCHAR2

Old status

SOURCE_NAME

NOT NULL

VARCHAR2

Source program name that processing the


payroll

SOURCE_ID

NOT NULL

NUMBER

Unique identifier of the programa that


processing the payroll

SOURCE_DESCRIPTION

CLOB

Description of the processing

CREATED_BY

NOT NULL

NUMBER

Standard who column

CREATION_DATE

NOT NULL

DATE

Standard who column

LAST_UPDATED_BY

NOT NULL

NUMBER

Standard who column

LAST_UPDATE_DATE

NOT NULL

DATE

Standard who column

NUMBER

Standard who column

LAST_UPDATE_LOGIN

Primary Key
Name

Column

Other Unique Keys


Name

Column

Check Constraints
Name

Column

Foreign Key
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

256

CLL_F357_GL_ACCT_HDR_OCCR_FK

HEADER_ID

Indexes
Name

Type

Sequence

Name of the Column

Sequences
Name

LAD Add-on Localizations

Column

EBS-PeopleSoft HCM Integration- Implementation Guide

257

You might also like