Campus Solutions 9.0 to EBS Financials (General Ledger ...

PeopleSoft Developer’s Reference Guide 

Campus Solutions 9.0 to EBS Financials 

(General Ledger) Integration Developer’s 

Reference Guide 

Authors: Renukeshwara Dev Ponnada, Viswanadha Rao Budidi

Campus Solutions 9.0 to EBS Financials (General Ledger) Integration Developer’s Reference Guide 

Copyright © 2009, Oracle. All rights reserved. 

The information contained in this document is proprietary and confidential to Oracle. 

No part of this document may be reproduced or transmitted in any form or by any 

means, electronic or mechanical, including photocopying and recording, for any 

purpose without the express written permission of Oracle. 

This document is provided for information purposes only and the contents hereof are 

subject to change without notice. This document is not warranted to be error-free, nor 

subject to any other warranties or conditions, whether expressed orally or implied in 

law, including implied warranties and conditions of merchantability or fitness for a 

particular purpose. We specifically disclaim any liability with respect to this document 

and no contractual obligations are formed either directly or indirectly by this document. 

This document may not be reproduced or transmitted in any form or by any means, 

electronic or mechanical, for any purpose, without our prior written permission. 

Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation 

and/or its affiliates. Other names may be trademarks of their respective owners. 

. 

© Copyright Oracle Corporation 2009. All rights reserved. 2

Table of Contents 

TABLE OF CONTENTS ................................................................................................................................................ 3 

INTRODUCTION .......................................................................................................................................................... 5 

Structure of this Developer’s Reference Guide ............................................................................................................ 5 

Related Materials .......................................................................................................................................................... 5 

FINANCIALS INTEGRATION OVERVIEW ................................................................................................................... 7 

ARCHITECTURE .......................................................................................................................................................... 8 

Figure 1: Functional Illustration ................................................................................................................................. 8 

Figure 2: Technical Illustration .................................................................................................................................. 9 

INTEGRATION SERVICES ........................................................................................................................................ 10 

Environment Setup .................................................................................................................................................. 10 

Pre-Requisite Setups .............................................................................................................................................. 10 

Create Database connection in JDeveloper to EBS Financials ...................................................................................... 10 

Synchronize Segments ............................................................................................................................................... 13 

Overview ................................................................................................................................................................. 13 

Step 1: Configure PeopleSoft .................................................................................................................................. 13 

Activate Service Operations ........................................................................................................................................... 13 

Activate Handlers ........................................................................................................................................................... 14 

Generate / Activate Routings .......................................................................................................................................... 15 

Set Routing Connection properties ................................................................................................................................. 16 

Set Queue status ............................................................................................................................................................ 16 

Provide Web Service and Generate WSDL URL ............................................................................................................ 17 

Step 2: Design the BPEL Process .......................................................................................................................... 20 

Database Adapter (DB Adapter) configuration for getting the Flexfield Segments from EBS GL ................................... 22 

Consuming Service configured in CS to publish the payload ......................................................................................... 27 

Output Transformation.................................................................................................................................................... 30 

Synchronize Segment Values ..................................................................................................................................... 36 

Overview ................................................................................................................................................................. 36 


Define Input / Output schemas ....................................................................................................................................... 36 

Creating Variables .......................................................................................................................................................... 40 

Partner Link Configuration .............................................................................................................................................. 43 

Connection Time Out configuration for Partner Link ....................................................................................................... 43 

Database Adapter (DB Adapter) configuration for getting the Flexfield Segment Values from EBS GL ......................... 50 

Alter the Input / Output XSD schema for the DB Adapter ............................................................................................... 51 

callbackClient configuration ............................................................................................................................................ 63 

Getting Endpoint location ............................................................................................................................................... 68 


Activate Service Operations ........................................................................................................................................... 68 




Set Queue status ............................................................................................................................................................ 73 

Provide Web Service and Generate WSDL URL ............................................................................................................ 73 

Publish Accounting Lines ............................................................................................................................................ 74 

© Copyright PeopleSoft Corporation 2009. All rights reserved. 3

Overview ................................................................................................................................................................. 74 


Define Input / Output schemas ....................................................................................................................................... 75 

Database Adapter (DB Adapter) configuration to insert data into GL_INTERFACE ....................................................... 78 

Transform payload to GL_INTERFACE .......................................................................................................................... 89 

Getting Endpoint location ............................................................................................................................................... 95 


Configure Service Operation STUDENT_FIN_ACCTG_LINE ........................................................................................ 97 

Activate Service Operation ............................................................................................................................................. 97 




Set Queue status .......................................................................................................................................................... 100 

Provide Web Service and Generate WSDL URL .......................................................................................................... 100 

Configure Service Operation STUDENT_ADV_ACCTG_LINE ..................................................................................... 100 

Activate Service Operation ........................................................................................................................................... 100 

Activate Handlers ......................................................................................................................................................... 101 

Generate / Activate Routings ........................................................................................................................................ 101 

Set Routing Connection properties ............................................................................................................................... 102 



Update Journal Info ................................................................................................................................................... 105 

Overview ............................................................................................................................................................... 105 

Step 1: Configure PeopleSoft ................................................................................................................................ 106 

Activate Service Operation ........................................................................................................................................... 106 






Step 2: Design the BPEL Process ........................................................................................................................ 113 

Define Input / Output schemas ..................................................................................................................................... 113 

Database Adapter (DB Adapter) configuration for getting Journal details from EBS .................................................... 116 

Update Journal Details Transformation ........................................................................................................................ 123 

Real-Time Code Combination Validation ................................................................................................................. 127 

Overview ............................................................................................................................................................... 127 

Step 1: Create PL/SQL package ........................................................................................................................... 128 

FND_SSF_CF_COMBO_VALIDATION package ......................................................................................................... 128 

Step 2: Design the BPEL Process ........................................................................................................................ 130 

Partner Link Configuration ............................................................................................................................................ 132 

Database Adapter (DB Adapter) configuration for invoking the validation routine on EBS ........................................... 133 

Getting Endpoint location ............................................................................................................................................. 142 

Step 3: Configure PeopleSoft ................................................................................................................................ 144 

Activate Service Operations ......................................................................................................................................... 144 






REFERENCES ......................................................................................................................................................... 147 

Mapping .................................................................................................................................................................... 147 

SF_ACCTG_LN to GL_INTERFACE mapping ..................................................................................................... 147 

AV_ACCTG_LN to GL_INTERFACE mapping ..................................................................................................... 152 

Journal Details mapping from EBS-GL to SF_ACCTG_LN and AV_ACCTG_LN ................................................ 156 

XSD Schema ............................................................................................................................................................ 157 



Introduction 

This Developer Reference Guide is a practical guide for technical users, installers, system administrators, and 

programmers who implement, maintain, or develop applications for your PeopleSoft system. In this Developer 

Guide, we would present an approach to integrate Campus Solutions (CS) with Oracle E-Business Suite Financials 

(EBS GL) using Oracle BPEL. 

The environment setup for the information contained in this document uses Oracle SOA Suite 10g (10.1.3.1). 

However, the same approach can be implemented when using other versions or Integration Solutions. 

STRUCTURE OF THIS DEVELOPER’S REFERENCE GUIDE 

This Developer Reference Guide is intended to be the first place for implementers to look for technical details on 

Integrating CS with EBS GL. The document provides a brief overview and architecture of the feature. Having 

insight into these will ensure more efficient and defect free implementations and minor customizations. This 

section provides an overview of the feature. In following sections each of the BPEL process and related setups on 

the CS side is reviewed. 

PeopleSoft updates this document as needed so that it reflects the most current feedback we receive from the field. 

Therefore, the structure, headings, content, and length of this document are likely to vary with each posted version. 

To see if the document has been updated since you last downloaded it, compare the date of your version to the 

date of the version posted on Customer Connection. 

RELATED MATERIALS 

This document is not intended to be a general introduction to environment tuning and we assume that the targeted 

readers are experienced IT professionals with a good understanding of PeopleSoft’s Internet Architecture, Oracle 

E-Business Suite and Integration Technologies. To take full advantage of the information covered in this document, 

we recommend that the reader have a basic understanding of Internet Architecture, web services, relational 

database concepts/SQL and database programming/PL SQL, and how to use PeopleSoft Application and Oracle 

E-Business suite. 

This document is not intended to replace the documentation delivered with PeopleTools. We recommend that 

before you read this document, you read the PIA related information and the Integration Broker concepts in the 

PeopleTools PeopleBooks to ensure that you have a well-rounded understanding of Integration technology. 

Many of the fundamental concepts related to PIA and Integration broker are discussed in the following PeopleSoft 

PeopleBooks: 

• Enterprise PeopleTools 8.49 PeopleBook: Internet Technology 

This PeopleBook provides an understanding of PeopleTools Internet technology, which consists of 

PeopleSoft Pure Internet Architecture. 

Refer to http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tprt/book.htm 

• Enterprise PeopleTools 8.49 PeopleBook: PeopleSoft Integration Broker 

This PeopleBook describes the processes for using PeopleSoft Integration Broker to develop and 

administer web services. 

Refer to http://download.oracle.com/docs/cd/E13292_01/pt849pbr0/eng/psbooks/tibr/book.htm 

© Copyright PeopleSoft Corporation 2009. All rights reserved. 5


Additionally, we recommend that you read the following BPEL documentation to gain a thorough understanding of 

the BPEL processes explained in this document: 

• Oracle BPEL Process Manager Quick Start Guide 10g (10.1.3.1.0) 

Refer to http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28983/toc.htm 

• Oracle BPEL Process Manager Developer's Guide 10g (10.1.3.1.0) 


• Oracle BPEL Process Manager Administrator's Guide 10g (10.1.3.1.0) 


This Developer Reference Guide has not been submitted for any formal testing process and has not undergone 

rigorous review. The material here is published as is. Oracle assumes no responsibility for its accuracy or 

completeness. The use of this information or the implementation of any of these techniques is a customer 

responsibility and depends upon the customer's ability to evaluate and integrate these techniques into their 

operational environments. 



Financials Integration Overview 

Student Financials currently integrates completely with Enterprise Financials. The chart of accounts, GL Business 

Unit details all come from Enterprise Financials. The Chartfield Combinations are also validated against valid data 

in Enterprise Financials (GL). There is a need to have similar full integration with Oracle 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 PeopleBooks. This integration involves the following components on 

the Campus Solutions end: 

• Setup to indicate usage of PeopleSoft Financials or Oracle Financials (General Ledger) or others 

• Associate GL Business Unit (GLBU) to Ledger, Operating Unit (OU) and Legal Entity(LE) in Oracle GL 

• Synchronize segment details and values from Oracle GL 

• Map existing Chartfields to Flexfield segments from COA in Oracle GL 

• Modify existing chartfield pages to support changes. Real-time validation of entered code combinations with Oracle GL 

• Transfer Accounting Lines (SF_ACCTG_LN and AV_ACCTG_LN) to Oracle GL Interface. 

To achieve this integration with Oracle Financials there is a need to develop some web services. This guide, details 

the technical details on developing web services to achieve this. 



Architecture 

Figure 1: Functional Illustration 

The above diagram provides high level details of Student Financials to Oracle Financials integration. 



Figure 2: Technical Illustration 

The above diagram illustrates the Technical approach for Student Financials to Oracle Financials integration. 



Integration Services 

Environment Setup 

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

1. Oracle SOA Suite 10g Release 3 (10.1.3) Patch Set 3(10.1.3.3.1). 

2. JDeveloper 10g (10.1.3.4). 

3. HCM 9.0 with PeopleTools 8.49 (release 18 and above). 

4. EBS R12 with Oracle Financials Release Update Pack 6 (R12.FIN_PF.A.DELTA.6). 

Pre-Requisite Setups 

Create Database connection in JDeveloper to EBS Financials 

A database connection has to be created in JDeveloper, which can be reused for DB adapter configuration across 

the BPEL processes. 

1. In the connection manager of JDeveloper, select Database. 

2. Right click and choose New Database Connection. 

3. It opens Create Database Connection wizard. 

4. Click Next. 



5. Provide a DB Connection name and Choose Oracle (JDBC) as Connection Type. 


7. Provide the database username and password. 




9. Leave the default for driver and provide the appropriate Host Name, JDBC port and SID for the database. 

(These details can be obtained from the TNS entry of the database) 


11. Click ‘Test Connection’ and verify that the status is Success, else revisit the above steps and verify the 

details. 

12. Click Finish. 



SYNCHRONIZE SEGMENTS 

Overview 

Source Application 

Target Application 

Process Type 

: EBS Financials (GL) 

: Campus Solutions (CS) 

: Asynchronous One-way 

The Synchronize Segments BPEL process is an Asynchronous process, which can be triggered either from 

Oracle Financials or BPEL console. 

All Active Flexfield segments in EBS Financials (GL) are fetched into a payload and pushed to Campus Solutions. 

The Notification Handler specified for the Service Operation takes care of parsing the XML payload and populating 

the respective tables with segment data. 

The data from segment synchronization process is used for: 

1. Mapping GL Business Unit (CS) to Ledger ID (GL). 

2. Mapping Chartfields (CS) to Segments (GL). 

The Development of Synchronize Segment service can be divided into a 2 step process. 

1. Configure PeopleSoft: Service and Routing configurations in PeopleSoft. 

2. Design the BPEL process: Designing the BPEL process. 

Step 1: Configure PeopleSoft 

Activate Service Operations 

1. Navigate to the Create and maintain Service Operations page: Main Menu > PeopleTools > 

Integration Broker > Service Operations. 

2. Search for the Service Operation SSF_GL_SEGMENT_FULLSYNC. 

3. In the General Tab activate the Service Operation by checking the Active checkbox as shown. 



4. Click Save. 

Activate Handlers 

1. In the above Service Operation navigation, for the same service operation 

SSF_GL_SEGMENT_FULLSYNC, go to the Handlers tab. 

2. Change the status of the OnNotifyManager to Active as shown below. 




Generate / Activate Routings 

1. Navigate back to the General tab and generate the Any to Local routing by checking the Generate Any-to- 

Local checkbox as shown below. 




Set Routing Connection properties 

Not Required. 

Set Queue status 

1. Navigate to the Maintain Queue’s page: Main Menu > PeopleTools > Integration Broker > Queues. 

2. Search for SSF_GL_INT. 

3. Change the Queue status to Run as shown. 




Provide Web Service and Generate WSDL URL 

1. Navigate to Provide web services page: Main Menu > PeopleTools > Integration Broker > Provide 

Web Service. 

2. In the Select services step, choose SSF_GL_SEGMENT_FULLSYNC as shown. 




4. In the Select Service Operations page, select the SSF_GL_SEGMENT_FULLSYNC.VERSION_1, as 

shown. 


6. In the view WSDL step, verify the WSDL and click Next. 

7. In the Specify Publishing Operations step, leave the defaults. 




9. This will complete the WSDL generation process and the WSDL URL is published. 

10. Make a note of the WSDL URL, as this will be provided for the partner link creation in the Design BPEL 

process step. 



Step 2: Design the BPEL Process 

In this step, we will use BPEL designer available as plug-in with JDeveloper, to create the BPEL process. 

Below are the steps involved in creating the BPEL process. Launch JDeveloper and follow steps given below: 

1. Select an Application, right click and go to New Project > BPEL Process Project. 

2. Provide Sync_GL_Segments for name and choose Asynchronous BPEL Process as type. Leave the 

remaining defaults. Click Next. 

0 

3. The process is triggered asynchronously and the payload pushed to Campus Solutions (CS) by consuming 

a service provided in CS, so there is no need to provide any Input or Output schemas. Leave the defaults 

and press Finish. 

4. The designer is presented with an empty asynchronous BPEL process. 



5. Double click the client partner link and change the Partner Link name client to Sync_GL_Segments. 

Verify that the Partner Role and My Role are as shown below, and click Apply, OK. 



Database Adapter (DB Adapter) configuration for getting the Flexfield Segments from EBS GL 

6. In the Component Palette select Services from drop list. Drag the Database Adapter and drop it onto the 

right Services swim lane. 

7. It opens up the Adapter Configuration Wizard. Click Next. 

8. Provide Get_Segments as the Service Name and a suitable description (e.g. Fetch flexfield segments 

from EBS GL) to the DB adapter. Click Next. 



9. Select the pre configured Database connection from drop down. Leave the default for JNDI name and click 

Next. 

10. In the Operation Type page select Execute Custom SQL and press Next. It opens up a page to enter the 

custom SQL. 



11. In the SQL section, provide the following custom SQL: 

SELECT gl.ledger_id AS ssf_ledger_id, 

gl.name 

AS ssf_ledger_name, 

fs.application_column_name AS ssf_segment_name, 

fs.flex_value_set_id AS ssf_segment_id, 

fs.segment_name 

AS ssf_segment_descr 

FROM gl_ledgers_public_v gl, 

fnd_id_flex_segments fs, 

fnd_application fapp 

WHERE fapp.application_short_name = 'SQLGL' 

AND fapp.application_id = fs.application_id 

AND fs.id_flex_code = 'GL' 

||Chr(35) 

AND fs.id_flex_num = gl.chart_of_accounts_id 

AND fs.enabled_flag = 'Y' 

AND gl.mrc_ledger_type_code 'R' 

ORDER BY gl.ledger_id, 

ssf_segment_name 

NOTE: The ID_FLEX_CODE needs to be compared to ‘GL’ || Chr(35) equivalent to ‘GL#’, ‘#’ being a 

reserved character for DB Adapter. 

12. The input / output XSD for the DB adapter is automatically generated and displayed in the XSD section. 

Click Next. 




14. Click on Apply and Ok. 



15. Under Component Palette select Invoke activity and drop it in-between the receiveInput and 

callbackClient activities. Rename it as Invoke_Get_Segments. 

16. Drag the right connector of the Invoke activity onto the Get_Segments DB adapter in the right swim lane. 



17. In the Edit Invoke dialog box, choose to auto create Input and Output variables. 

18. Click Apply and OK. 

Consuming Service configured in CS to publish the payload 

19. Select Partner Link under services from Component Palette and drop into right swim lane in the Flow 

diagram. 



20. This opens up a Partner Link edit dialog. 

21. Under the WSDL File, provide the WSDL URL generated in Provide Web Service and Generate WSDL 

URL section of Configure PeopleSoft step. 



22. Select the partner Link Type and select the Partner Role as Provider as shown: 

23. Leave the remaining defaults and click OK. 

24. Select Invoke activity and drop it in-between the Invoke_Get_Segments and callbackClient activities. 

Rename it as Invoke_Publish_Segments. 

25. In the Edit Invoke dialog box, choose to auto create Input variables. 

Note: There will not be an output variable for this Invoke activity, as this is a one-way consume service on 

BPEL side. 



Output Transformation 

26. The output from the DB adapter needs to be transformed into the output payload. Drag the Transform 

activity from the Process Activities selection in Component Palette and drop it onto flow diagram inbetween 

the Invoke_Get_Segments and Invoke_Publish_Segments activities as shown. 



27. Edit the transform activity by double clicking it. 

a) Under the ‘General’ tab, rename it to Transform_Segments. 

b) Under the ‘Transformation’ tab, configure the Input and output variables as follows: 

Source variable: Invoke_Get_Segments_Get_Segments_Output_Variable of Get_Segments DB 

adapter. 

Target variable: Invoke_Publish_Segments_SSF_GL_SEGMENT_FULLSYNC_InputVariable of 

SSF_GL_SEGMENT_FULLSYNC DB adapter. 

c) Under the Mapper Configuration, rename the mapper file to Transformation_Segments.xsl. 



d) Click OK. 

e) It opens up a Transformation mapper. Perform the mapping as shown below: 



f) Save the Transformation and Close it. 

28. Select the project in the Project Navigator, right click and select to deploy as shown. 



29. Once the Process is compiled and deployed without errors, it can be verified and tested from the BPEL 

console. 





SYNCHRONIZE SEGMENT VALUES 

Overview 



Process Type 

: Campus Solutions (CS) 

: EBS Financials (GL) 

: Asynchronous Two-way 

Synchronize Segment values is an Asynchronous BPEL process initiated from Campus Solutions, through a run 

control page. 

The process can be run in two modes from the run control page: 

a) Full sync: Ledger Id’s for all the mapped GL Business Units, all Segment Id’s mapped to the GL Business 

Unit and a Last Sync Date value of 01/01/1900 is passed to the BPEL process. 

b) Partial sync: Ledger Id and Segment Id’s are selected by the user and are passed to the BPEL process. 

The Last Sync Date is derived and passed for each Segment to facilitate incremental sync. 

The process returns all the Segment values for the corresponding Ledger Id and the Segment Id passed. The 

handler configured at the Campus Solutions parses the payload and populates the respective tables. 

The data returned by the process is used to populate the underlying chartfield prompt tables, based on Chartfield to 

Segment mapping. 

The Development of Synchronize Segment values service can be divided into a 2 step process. 





1. Select the Application right click and choose New Project > BPEL Process Project. 

2. Provide Sync_GL_Segment_Values for name and choose Asynchronous BPEL Process as type. Leave 

the remaining defaults. Click Next. 

Define Input / Output schemas 

3. Input / Output Elements wizard opens up. Click on Browse to provide the Input and Output XSD 

definitions. The steps to get the respective XSD definitions are explained: 



4. Input / Output schema definitions for this BPEL process can be obtained as follows: 

i) Input schema: 

Navigation: 

Message Name: 

Version Number: 

Campus Solutions Portal > PeopleTools > Integration Broker > Messages 

SSF_GL_SEGMENT_VAL_REQ 

VERSION_1 

Go to schema tab to obtain the schema associated with the message. 



This is the schema for the Outbound request message from Campus Solutions which will be used as 

Input schema for the BPEL process. 

Make a local copy of the XSD and point to the XSD from the Input / Output elements wizard. After 

selecting the XSD definition, the user is presented with a Type Chooser wizard. Select the 

SSF_LEDGER_ID element as shown: 



Click Ok. 

ii) 

Output schema: 

Navigation: 

Message Name: 



SSF_GL_SEGMENT_VAL_REQ 

VERSION_1 

Go to schema tab to obtain the schema associated with the message. Make a local copy of the XSD 

and point to the XSD from the Input / Output elements wizard. After selecting the XSD definition, select 

the SSF_LEDGER_ID element as shown: 



Click Ok. 


6. The designer is presented with an empty asynchronous BPEL process. 

Creating Variables 

The following variables need to be created and will be used during the BPEL flow. 

Variable Name 

Node_Count 

Loop_Index 

Batch_Size 

Date_Part_String 

Last_Sync_Date_Var 

Loop_Index_SegVal 

Node_Count_SegVal 

Variable Type 

Simple Type: Long 



Simple Type: String 

Simple Type: Date 





The step to create the Node_Count variable is mentioned below: 

I. In the BPEL structure pane, navigate the tree to BPEL Structure > Variables > Process > Variables. 

Right click on Variables and select Create Variable. 

II. 

In the create variable dialog provide Node_Count for name and select Simple Type for variable type. Click 

on Browse to choose the type from XML schema types. 



III. 

IV. 

Select long and click Ok. 

Click Apply and Ok. 

Repeat above steps for creating the remaining variables. 



Partner Link Configuration 

7. Double click the client partner link and change the Partner Link name “client” to 

Sync_GL_Segment_Values. Verify that the Partner Link type, Partner Role and My Role are as shown 

below. 

8. Click Apply and Ok. 

Connection Time Out configuration for Partner Link 

In PeopleSoft, the Maximum App Message Size value governs the maximum size of the payload, 

Integration Broker can handle. (Main Menu > PeopleTools > Utilities > PeopleTools Options) 



The Synchronize Segments Values BPEL process returns large number of Segment values and if the 

payload exceeds the Maximum App Message Size, IB cannot handle it. Hence, the payload in the BPEL 

process needs to be chunked and sent out to IB in batches. 

However, whenever there is a response back from the callbackClient to the invoking partner link, the 

connection closes after first response. If callbackClient tries to send another set of payload to the partner 

link, it errors out with the connection TIMEOUT error. Hence, we need to configure the partner link to keep 

the connection alive for a certain period of time. 

The chunking and de-batching of the payload can be configured in a 3 step process. 

a) Setting TIMEOUT property for partner link: Since the payload is chunked and sent in batches, there 

will be multiple Callbacks. To keep the connection open after the first call back, we need to set the 

TIMEOUT property of the partner link to a higher value (say 100000). This keeps the connection open 

from the partner link for specified time. 

b) Setting the chunk or batch size: Using an assign activity, we set the batch size during the BPEL flow, 

which will be used to chunk the payload. Steps for creating this activity are discussed in steps below. 

c) De-batching the Payload based on preset batch size: The payload is de-batched to the limit of 

batch size preset in earlier step and sent through Callback. The steps to de-batch are explained in 

steps down below. 

9. Setting the TIMEOUT property: Double click the Sync_GL_Segment_Values partner link and go to 

Property tab. Click Create and in the dropdown list for Name, select timeout property. Select Ok. In the 

property value text area replace the default text with 100000. Click Apply and Ok. 



10. Drag an assign activity from the list of Process Activities onto the BPEL flow diagram after the 

receiveInput activity. Rename the activity to Set_Batch_Size as shown: 

11. Double click the Set_Batch_Size activity and go to Copy Operation tab. Select Copy Operation from the 

Create dropdown. It opens Create Copy Operation window. 

12. In the From side, select Expression as type and enter 50 in the text area. In the To side, select Variable as 

Type and select Batch_Size from the Variables list as shown: 



13. Click Ok. 

14. Drag an assign activity from the list of Process Activities into the BPEL flow diagram and place it after the 

Set_Batch_Size activity. Rename the activity to Initialize_loopIndex_n_nodeCount. 

15. Configure the activity as shown below: 

Operation 

type 

From type 

From (Expression / XPATH / XML 

Fragment) 

To type 

To (Expression / 

XPATH / XML 

Fragment) 

Copy Expression 1 Variable Loop_Index 

Copy 

Expression 

ora:countNodes('inputVariable','payload',' 

/ns1:SSF_LEDGER_ID/ns1:SSF_GL_SE 

GMENT_NAME') Variable Node_Count 

16. Drag and drop a While activity onto the BPEL flow after the Initialize_loopIndex_n_nodeCount activity. 

17. Provide the following conditional expression to the above while loop: 

bpws:getVariableData('Loop_Index')


18. Add an Assign activity within the while loop and rename it as Increment_loopIndex. Add the below copy 

operation to this activity: 

Operation 

type 

From type 


Fragment) 

To type 


XPATH / XML 

Fragment) 

Copy Expression bpws:getVariableData('Loop_Index') + 1 Variable Loop_Index 



19. Drag an Assign activity before the Increment_loopIndex activity within the while loop and rename it as 

Format_LASTSYNC_Date. Create the operations for this Assign activity as mentioned in the below table: 

Operation 

type 

From type 


Fragment) 

To type 


XPATH / XML 

Fragment) 

Copy 

Copy 

Copy 

Copy 

Variable 

Expression 

Expression 

Expression 

/ns1:SSF_LEDGER_ID/ns1:SSF_GL_SE 

GMENT_NAME[bpws:getVariableData('L 

oop_Index')]/ns1:SSF_LASTSYNC_DT Variable Last_Sync_Date_Var 

translate(substring(bpws:getVariableData 

('Last_Sync_Date_Var'),12,8),'.',':') Variable Date_Part_String 

concat(bpws:getVariableData('Date_Part 

_String'),substring(bpws:getVariableData( 

'Last_Sync_Date_Var'),20,4)) Variable Date_Part_String 

concat(substring(bpws:getVariableData(' 

Last_Sync_Date_Var'),1,10),"T",bpws:get 

VariableData('Date_Part_String')) Variable Last_Sync_Date_Var 



20. Drag an Assign activity and rename it as Initialize_Get_Segment_Values_Params. Create the operations 

for this Assign activity as mentioned in the below table: 

Operation 

type 

From 

type 

From (Expression / XPATH / 

XML Fragment) 

To type 

To (Expression / XPATH / 

XML Fragment) 

Copy Variable /ns1:SSF_LEDGER_ID/@value Variable 

/ns3:Get_Segment_ValuesInput 

/ns3:PARAM_LEDGER_ID 

Copy 

Variable 

/ns1:SSF_LEDGER_ID/ns1:SSF_ 

GL_SEGMENT_NAME[bpws:getV 

ariableData('Loop_Index')]/ns1:SS 

F_SEGMENT_ID 

Variable 


/ns3:PARAM_SEGMENT_ID 

Copy Variable Last_Sync_Date_Var Variable 


/ns3:PARAM_LAST_SYNC_DA 

TE 



21. Rename the default sequence name for the While Loop to For_Each_Segment_Id as shown below: 

Database Adapter (DB Adapter) configuration for getting the Flexfield Segment Values from 

EBS GL 

22. Choose Database adapter from the services pane and drop it into right swim lane. Configure the DB 

adapter as described below: 



DB Adapter name 

Description 

Connection 

Operation Type 

SQL 

Get_Segment_Values 

Get Segment Values 

 

Execute Custom SQL 

SELECT ffv.FLEX_VALUE as SSF_SEG_VALUE, ffv.DESCRIPTION 

as SSF_SEG_DESCR, ffv.LAST_UPDATE_DATE as 

SSF_SEG_EFFDT, ffv.ENABLED_FLAG as SSF_SEG_STATUS 

FROM FND_ID_FLEX_SEGMENTS fifs, FND_FLEX_VALUES_VL ffv, 

FND_APPLICATION fapp WHERE 

fapp.APPLICATION_SHORT_NAME = 'SQLGL' AND 

fifs.APPLICATION_ID = fapp.APPLICATION_ID AND 

fifs.ID_FLEX_CODE = 'GL' || CHR(35) AND fifs.ID_FLEX_NUM = 

(SELECT CHART_OF_ACCOUNTS_ID FROM 

GL_LEDGERS_PUBLIC_V WHERE LEDGER_ID= 

#PARAM_LEDGER_ID) AND fifs.FLEX_VALUE_SET_ID = 

ffv.FLEX_VALUE_SET_ID AND ffv.FLEX_VALUE_SET_ID = 

#PARAM_SEGMENT_ID AND TRUNC(SYSDATE) BETWEEN 

TRUNC(NVL(ffv.START_DATE_ACTIVE,SYSDATE)) AND 

TRUNC(NVL(ffv.END_DATE_ACTIVE,SYSDATE)) AND 

ffv.LAST_UPDATE_DATE > #PARAM_LAST_SYNC_DATE 

23. Select the Partner Link Type and Role as shown: 

Alter the Input / Output XSD schema for the DB Adapter 

24. Open the Get_Segment_Values.xsd definition in the Application Navigator under schemas as shown: 



25. Modify the Element Name and the Complex Type Name from Get_Segment_ValuesOutput to 

SSF_GL_SEGMENT_VAL as shown: 

26. Select the Invoke activity from the services pane and drop it onto BPEL flow after the 

Initialize_Get_Segment_Values_Params activity. 

27. Rename the invoke activity as Invoke_Get_Segment_Values and associate it with the 

Get_Segment_Values DB adapter. This invokes an Edit invoke dialog. 



28. Use Auto Create to automatically create both Input and Output variables for the Invoke activity based on 

the query provided to the associated DB adapter: 






30. Add a Scope activity to the BPEL flow after the Invoke_Get_Segment_Values activity. 

31. Add variables Loop_Index_SegVal and Node_Count_SegVal to the scope as shown below: 

32. Add an Assign activity into the above scope and rename it as 

Initialize_loopIndex_n_nodeCount_For_SegVals. Add the following operations to this activity: 

Operation 

type 

From 

type 


XML Fragment) 

To type 


XML Fragment) 

Copy 

Express 

ion 1 Variable Scope_1: Loop_Index_SegVal 

Copy 

Express 

ion 

ora:countNodes('Invoke_Get_Seg 

ment_Values_Get_Segment_Valu 

es_OutputVariable','Get_Segment 

Variable 

Scope_1: Node_Count_SegVal 



_ValuesOutputCollection','/ns3:Ge 

t_Segment_ValuesOutputCollecti 

on/ns3:SSF_GL_SEGMENT_VAL' 

) 

33. Add an Assign activity after the Initialize_loopIndex_n_nodeCount_For_SegVals, and rename it as 

Update_Ledger_Id_n_Segment_Name. Add the Operations mentioned below to this Assign Activity: 

Operation 

type 

From 

type 


XML Fragment) 

To type 


XML Fragment) 

 

Copy 

XML 

Fragme 

nt 

 

 

Variable 

variable="outputVariable" 

part="payload" 

Copy Variable /ns1:SSF_LEDGER_ID/@value Variable /ns4:SSF_LEDGER_ID/@value 

Copy 

Variable 

/ns1:SSF_LEDGER_ID/ns1:SSF_ 

GL_SEGMENT_NAME[bpws:getV 

ariableData('Loop_Index')]/@valu 

e 

Variable 

/ns4:SSF_LEDGER_ID/ns4:SS 

F_GL_SEGMENT_NAME/@val 

ue 



34. Rename the sequence name to Set_Of_Segment_Vals_For_Each_Segment_Id as shown: 

35. Add a While activity after the Update_Ledger_Id_n_Segment_Name activity and provide the below 

expression as Condition Expression: 

bpws:getVariableData('Loop_Index_SegVal')


36. Add an Assign activity within the while loop and rename it as Increment_LoopIndex_SegVals. Add the 

below Copy operation to this activity: 

Operation 

type 

From 

type 


XML Fragment) 

To type 


XML Fragment) 

Copy 

Express 

ion 

bpws:getVariableData('Loop_Inde 

x_SegVal') + 1 Variable Loop_Index_SegVal 



37. Add an Assign activity within the while loop before the Increment_LoopIndex_SegVals activity and 

rename it as Append_Segment_Values. Add the following Append Operations to this Assign activity: 

Operation 

type 

From 

type 


XML Fragment) 

To type 


XML Fragment) 

variable="Invoke_Get_Segment_ 

Values_Get_Segment_Values_O 

utputVariable" 

Append 

Variable 

part="Get_Segment_ValuesOutp 

utCollection" 

query="/ns4:Get_Segment_Value 

sOutputCollection/ns4:SSF_GL_S 

EGMENT_VAL[bpws:getVariable 

Data('Loop_Index_SegVal')]” 

Variable 



query="/ns2:SSF_LEDGER_ID/ 

ns2:SSF_GL_SEGMENT_NAM 

E" 

Note: The Invoke_Get_Segment_Values_Get_Segment_Values_OutputVariable and 

Invoke_Get_Segment_Values_Get_Segment_Values_InputVariable are the auto created variable from 

the Get_Segment_Values DB Adapter. 

38. Add a Switch Case after the Append_Segment_Values activity. 

39. Rename the Sequence name for the activities within the while loop to Debatching_Segment_Values as 

shown: 



40. For the above Switch Case, provide the below expression as the Condition expression: 

(bpws:getVariableData('Loop_Index_SegVal') mod bpws:getVariableData('Batch_Size') = 0) or 

(bpws:getVariableData('Loop_Index_SegVal') = bpws:getVariableData('Node_Count_SegVal')) 

41. Move the callbackClient of the Asynchronous process into the Switch Case branch as detailed below: 



42. Add an Assign activity after the callbackClient and rename it as 

Re_Update_Ledger_Id_n_Segment_Name. Add the following operations to the assign activity as detailed 

below: 

Operation 

type 

From 

type 


XML Fragment) 

To type 


XML Fragment) 

Copy 

XML 

Fragme 


nt 

xmlns="http://www.example.org"> 


 

 

variable="inputVariable" 




Copy 

Variable 


@value" 

Variable 


@value" 

variable="inputVariable" 




Copy 

Variable 

query="/ns1:SSF_LEDGER_ID/n 

s1:SSF_GL_SEGMENT_NAME[b 

pws:getVariableData('Loop_Index' 

)]/@value" 

Variable 


ns4:SSF_GL_SEGMENT_NAM 

E/@value" 

43. Rename the sequence of activities within the Switch case to Send_Batch as shown: 



callbackClient configuration 

44. In Campus Solutions, navigate to Main Menu > PeopleTools > Integration Broker > Service Operations 

and search for SSF_GL_SEGMENT_VAL_SYNC. 

45. Go to routings tab and click on Inbound routing as shown: 



46. It opens Routing definition page, go to Parameters tab. 

47. Note the External Alias for the Inbound request which is SSF_GL_SEGMENT_VAL_SYNC.VERSION_1. 

48. In the BPEL designer, open the Sync_GL_Segment_Values.wsdl WSDL file in source mode and replace 

the name of onResult operation with SSF_GL_SEGMENT_VAL_SYNC.VERSION_1 as shown: 



49. Save the WSDL file and open the callbackClient in the BPEL designer, and change the Operation to 

SSF_GL_SEGMENT_VAL_SYNC.VERSION_1 as shown: 




51. Save the BPEL process and select the project in the Project Navigator, right click and select to deploy. 

52. Verify that the Process is compiled and deployed successfully without errors. 





Getting Endpoint location 

After the BPEL process is deployed, navigate to the BPEL console and obtain the Endpoint Location for the 

Synchronize Segment values BPEL process as shown: 



1. Navigate to the Create and maintain Service Operations page: Main Menu > PeopleTools > 

Integration Broker > Service Operations. 

2. Search for the Service Operation SSF_GL_SEGMENT_VAL_SYNC. 

3. In the General Tab activate the Service Operation by checking the Active checkbox as shown. 





1. In the above Service Operation navigation for the same service operation 

SSF_GL_SEGMENT_VAL_SYNC, go to the Handlers tab. 

2. Change the status of the OnNotifyManager to Active as shown below. 





1. Navigate back to the General tab and generate the Any to Local routing by checking the Generate Any-to- 

Local checkbox as shown below. 




3. Navigate to the Routings tab and verify that the SSF_GL_SEGMENT_VAL_SYNC routing is active. 


1. Click on the SSF_GL_SEGMENT_VAL_SYNC routing to navigate to the connection properties page. 



2. On the Routings page, go to Connection Properties tab. For the Primary URL field provide the Endpoint 

Location URL obtained in the BPEL process Design step. 





1. Navigate to the Maintain Queue’s page: Main Menu > PeopleTools > Integration Broker > Queues. 


3. Change the Queue status to Run as shown. 



Not Required. 



PUBLISH ACCOUNTING LINES 

Overview 



Process Type 

: Campus Solutions(CS) 

: EBS Financials(GL) 


Currently the CS Enterprise Components Batch Publish utility is used to publish Accounting lines from Student 

Financials (SF) and Contributor Relations (AV) to FDM (PSFT Enterprise Financials) database. The following two 

IB messages have being used by Batch Publish. 

a. STUDENT_FIN_ACCTG_LINE message for SF_ACCTG_LN data. 

b. STUDENT_ADV_ACCTG_LINE message for AV_ACCTG_LN data (CR accounting lines). 

To integrate with EBS GL, both SF_ACCTG_LN and AV_ACCTG_LN data has to be published to GL_INTERFACE 

table in EBS database. The data published from the above messages has to be transformed and inserted into 

GL_INTERFACE. The IB message has to be transformed and sent to a BPEL process which would insert the 

transformed data into GL_INTERFACE. 

See mapping details section in this document for details on mapping content from SF_ACCTG_LN and 

AV_ACCTG_LN to GL_INTERFACE. 


Following are the steps to create BPEL Process to insert data into GL_INTERFACE. 

1. Create a new Asynchronous BPEL Process. Name the process Insert_GL_Interface. Click Next. 




2. Click the Input Schema Element Browse button and provide the schema definition as indicated in the XSD 

Schema reference section. 



3. Upon selecting the SSF_ACCTG_LINE_TRFM_EBGL.xsd file, it shows the following Type Chooser 

window. Select GL_INTERFACE_TBL type and click OK. 

4. Ensure that the right Input Schema Element selected and click Finish. 



5. A new Insert_GL_Interface.bpel file would be created and the design view would be shown in the BPEL 

Designer (JDeveloper). Double click Client partner link to edit. 



6. It opens Edit Partner Link window. Change the partner link name to Insert_GL_Interface, in the General 

Tab. Click Apply and OK. 

Database Adapter (DB Adapter) configuration to insert data into GL_INTERFACE 

7. Select Services from drop list in the Component Palette. Drag the Database Adapter and drop it onto the 

right Services swim lane. This action opens Adapter Configuration wizard. 



8. Click Next on the Adapter Configuration Wizard - Welcome window. 



9. Enter Service Name GL_Interface_Insert and Description “Insert into GL_INTERFACE”. Click Next. 

10. Select the database connection and leave all other fields to default values. Click Next. 



11. Select Perform an Operation on a Table Radio button and check the Insert Only check box. Click Next. 

12. Click on Import Tables button. 



13. Query for GL_INTERFACE table. It retrieves the objects into Available List. Select GL_INTERFACE from 

the available list and click “>” button. Click OK. 

14. Click Next on the Select Table window. 



15. Select all primary keys for the GL_INTERFACE in the Define Primary Keys window. Click Next. Following 

are the Primary keys for the GL_INTERFACE table. 

o 

o 

o 

o 

o 

o 

o 

o 

o 

STATUS 

LEDGER_ID 

ACCOUNTING_DATE 

CURRENCY_CODE 

DATE_CREATED 

CREATED_BY 

ACTUAL_FLAG 

USER_JE_CATEGORY_NAME 

USER_JE_SOURCE_NAME 



16. Click Next on the Relationships window. 



17. Click Finish. It opens a Create Partner Link window. 

18. Click Apply, OK. 



19. Select Process Activities from drop list in the Component Palette. Drag the Invoke activity and drop it 

between receiveInput and callbackClient activities. 

20. Double click on the Invoke activity to edit. 



21. Change the name to Invoke_GLInt_Insert in General Tab. Click “Browse” button for Partner Link. 

22. Choose GL_Interface_Insert Partner Link from Partner Link Chooser. Click OK. 



23. Click on Automatically create Input Variable button. It opens Create Variable window. 

24. Change the name to “Invoke_GLInt_Insert_InputVariable”. Click OK. 

25. Click Apply, OK on Invoke window. 



Transform payload to GL_INTERFACE 

26. Select Process Activities from drop list in the Component Palette. Drag the Transform activity and drop it 

between receiveInput and Invoke_GLInt_Insert activities. 

27. Double click on the Transform activity to edit. 



28. Change the name to Transform_Input_GLInterface in General Tab. 

29. Navigate to Transformation Tab, select Source and Target Variables as mentioned below. 

o 

o 

Source Variable: inputVariable 

Target Variable: Invoke_GLInt_Insert_InputVariable 



30. Change Mapper file name to Transformation_Input and Click on Create Mapping button to create 

transformation file. 

31. Create mapping by dragging and dropping as shown in below. It opens up Auto Map preferences window. 



32. Verify for correct mapping and click OK. 



33. The Auto map feature maps only similar fields. Map the remaining fields by dragging and dropping the 

fields. 



34. Save the Transformation_Input.xsl and close it. 





36. Build and deploy Insert_GL_Interface BPEL Process to the default domain. After successful deployment 

of the process, make a note of the “Endpoint location” of the process. This would be used to configure 

routings in PeopleSoft Integration Broker. 






Configure the following two service operations as mentioned. 

a. STUDENT_FIN_ACCTG_LINE 

b. STUDENT_ADV_ACCTG_LINE 

Configure Service Operation STUDENT_FIN_ACCTG_LINE 

Activate Service Operation 

1. Navigate to the “Create and maintain Service Operations” page: Main Menu > PeopleTools > Integration 

Broker > Service Operations. 

2. Search for the Service Operation “STUDENT_FIN_ACCTG_LINE”. 

3. In the General Tab, activate the Service Operation by checking the “Active” checkbox as shown. 

4. Click “Save”. 




Not Required. 


1. Navigate to the Routings Tab on the same Service Operations page. 

2. Activate the Routing “SSF_SFACCTGLN_EBGL_WSDL” checking the “Selected” checkbox as shown. 

3. Click “Activate Selected Routings” 





5. Navigate to Routings page by clicking on Routing hyperlink “SSF_SFACCTGLN_EBGL_WSDL” as shown. 

6. Navigate to Connector Properties Tab as shown. 

7. Provide Endpoint location URL of Insert_GL_Interface BPEL Process (Mentioned above in Design 

BPEL Process section) in the value field of PRIMARYURL Property ID. 





Not required. 


Not Required. 

Configure Service Operation STUDENT_ADV_ACCTG_LINE 




10. Search for the Service Operation “STUDENT_ADV_ACCTG_LINE”. 

11. In the General Tab, activate the Service Operation by checking the “Active” checkbox as shown. 





Not Required. 


13. Navigate to the Routings Tab on the same Service Operations page. 

14. Activate the Routing “SSF_AVACCTGLN_EBGL_WSDL” checking the “Selected” checkbox as shown. 

15. Click “Activate Selected Routings” 





17. Navigate to Routings page by clicking on Routing hyperlink “SSF_AVACCTGLN_EBGL_WSDL” as shown. 

18. Navigate to “Connector Properties” Tab as shown. 

19. Provide Endpoint location URL of Insert_GL_Interface BPEL Process (Mentioned above in Design 

BPEL Process section) in the value field of PRIMARYURL Property ID. 





21. Navigate to the maintain Queue’s page: Main Menu > PeopleTools > Integration Broker > Queues. 

22. Search for STUDENT_ADMIN_ACCOUNTING. 

23. Set the Queue status to Run as shown. 





Not required. 



UPDATE JOURNAL INFO 

Overview 



Process Type 




The Update Journal Details BPEL process is an asynchronous process, which can be triggered either from Oracle 

Financials or BPEL console. 

Once journaling has been done in GL, the status of individual transactions posted from CS with additional journal 

information needs to be sent back to CS. On completion of the Journaling process in EBS Financials (GL), this 

process updates SF/AV Accounting lines with journal details. This BPEL process fetches the journal details, 

creates a payload and pushes the xml payload to CS. The Notification Handler specified for the Service Operation 

takes care of parsing the XML payload and updating the respective tables’ data. 

See mapping details in mapping section of this document for details on Journal Details mapping from EBS-GL to 

SF_ACCTG_LN and AV_ACCTG_LN. 

The data updated from this process can be viewed in the following pages: 

1. Review Accounting Lines / Review GL Integration Data 

2. Accounting Line Summary (CR) 

The Development of Update Journal Details service can be divided into a 2 step process. 









2. Search for the Service Operation “SSF_GL_ACCTG_LINE_SYNC”. 

3. In the General Tab activate the Service Operation by checking the “Active” checkbox as shown. 





1. In the above Service Operation navigation for the same service operation 

“SSF_GL_ACCTG_LINE_SYNC”, go to the Handlers tab. 

2. Change the status of the OnNotifyManager handler to “Active” as shown below. 



5. Navigate back to the General tab and generate the Any to Local routing by checking the “Generate Anyto-Local” 

checkbox as shown below. 




7. Navigate to Routings Tab and ensure that the Any-to-Local routing has been created and made Active. 




Not Required. 


1. Navigate to the maintain Queue’s page: Main Menu > PeopleTools > Integration Broker > Queues. 


3. Ensure that the Queue status is set to Run as shown (If not, set to Run). 





1. Navigate to “Provide web services” page: Main Menu > PeopleTools > Integration Broker > Provide Web 

Service. 

2. In the Select services step, search for “SSF_GL_ACCTG_LINE_SYNC” and select the service by checking 

the check box as shown. 


4. In the Select Service Operations page, select the “SSF_GL_ACCTG_LINE_SYNC”, VERSION_1, as 

shown. 


6. In the view WSDL step, verify the WSDL and click Next. 



7. In the Specify Publishing Operations step, leave the defaults. 


9. This will complete the WSDL generation process and the WSDL URL is published. 



10. Make a note of the WSDL URL, as this will be provided for the partner link creation in the Design BPEL 

process step. 




Follow the steps to create BPEL Process to update SF/AV Accounting lines with Journal Details: 

1. Create a new Asynchronous BPEL Process. Name the process UPD_JournalDetails. Click Next. 

2. Leave the defaults for Input and Output Schema Elements and click Finish. This process would be 

triggered from the BPEL Console with Ledger ID, JE Source Name and Group ID as inputs. Hence, the 

Input Schema Element has to be modified. 


3. In the Applications Navigator, navigate to UPD_JournalDetails > Integration Content > Schemas. Open 

UPD_JournalDetails.xsd schema file and go to source view. Copy & paste the following xsd to 

UPD_JournalDetails.xsd and save. 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

4. Go to design view of the xsd. The edited xsd is as shown below. 

5. The designer is presented with an empty asynchronous BPEL process. Ensure that the inputVariable got 

generated correctly. (Double click on receiveInput activity and browse for input variable.) The edited 

inputVariable is as shown below. 



6. Double click the client partner link and change the Partner Link name “client” to “UPD_JournalDetails”. 

Verify that the Partner Role and My Role are as shown below, and click Apply, OK. 



Database Adapter (DB Adapter) configuration for getting Journal details from EBS 

7. In the Component Palette select Services from drop list. Drag the Database Adapter and drop it onto the 

right Services swim lane. It opens up the “Adapter Configuration Wizard”. Click Next. 

8. Configure the DB adapter as shown below: 

DB 

Adapter 

name 

Descriptio 

n 

Connectio 

n 

Operation 

Type 

SQL 

XSD 

getJournalDetails 

Get Journal Details from EBS 

 

Execute Custom SQL 

SELECT GL_JE_LINES.REFERENCE_10 AS RECNAME 

,GL_JE_LINES.REFERENCE_4 AS RUN_DT 

,GL_JE_LINES.REFERENCE_6 AS SEQNUM 

,GL_JE_LINES.REFERENCE_7 AS SF_LINE_NBR 

,GL_JE_LINES.JE_HEADER_ID AS JOURNAL_ID 

,TO_CHAR(GL_JE_HEADERS.DATE_CREATED,'YYYY-MM-DD') AS 

JOURNAL_DATE 

,GL_JE_LINES.JE_LINE_NUM AS JOURNAL_LINE 

,GLP.PERIOD_YEAR AS FISCAL_YEAR 

,GLP.PERIOD_NUM AS ACCOUNTING_PERIOD 

,GL_JE_BATCHES.GROUP_ID AS PROCESS_INSTANCE 

,GL_JE_LINES.STATUS AS GL_DISTRIB_STATUS 

FROM GL_JE_LINES 

,GL_JE_BATCHES 

,GL_JE_HEADERS 

,GL_PERIODS GLP 

WHERE GL_JE_BATCHES.GROUP_ID = #GROUP_ID 

AND GL_JE_HEADERS.JE_BATCH_ID = GL_JE_BATCHES.JE_BATCH_ID 

AND GL_JE_HEADERS.JE_HEADER_ID = GL_JE_LINES.JE_HEADER_ID 

AND GL_JE_HEADERS.JE_SOURCE = (SELECT JE_SOURCE_NAME 

FROM GL_JE_SOURCES 

WHERE 

USER_JE_SOURCE_NAME = #JE_SOURCE_NAME) 

AND GL_JE_HEADERS.LEDGER_ID = #LEDGER_ID 

AND GLP.PERIOD_NAME = GL_JE_LINES.PERIOD_NAME 

AND GLP.PERIOD_SET_NAME = GL_JE_BATCHES.PERIOD_SET_NAME 

ORDER BY JOURNAL_ID,JOURNAL_LINE 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Note: In the Custom SQL window, provide the following SQL and XSD in the respective fields. Click Next. 

(While providing SQL, XSD would be automatically generated. But it may vary based on the SQL 

indentation. Hence, we have to edit the generated XSD.) 



9. Click Finish in the final step. It generates xsd and wsdl files and opens up a Create Partner Link window. 

Click Apply and OK. 



10. Under Component Palette select Invoke activity and drag and drop it in-between the receiveInput and 

callbackClient activities. Edit the invoke activity by double clicking on it. 

11. Rename the invoke activity to “Invoke_getJournalDetails”. Select Partner Link as getJournalDetails and 

Operation as getJournalDetails. 

12. Create Input and Output variables for this activity by clicking Automatically Create Variable buttons. 

Provide names for these variables as shown. 

13. Click Apply and OK on the Invoke activity window. 



14. Select ‘Partner Link’ under services from Component Palette, drag and drop onto right swim lane in the 

Flow diagram. This action opens up a Create Partner Link dialog. 

15. Under the WSDL File, provide the WSDL URL generated at Generate WSDL URL section of Configure 

PeopleSoft and tab out. It populates the partner link name automatically. (Make sure that app server and 

web server are running without any issues.) Select Partner Link Type and Partner Role as shown. Click 

Apply and OK. 



16. Under Component Palette select Invoke activity and drag and drop it in-between the 

Invoke_getJournalDetails and callbackClient activities. Edit the invoke activity by double clicking on it. 

17. Rename the invoke activity to “Invoke_SSF_GL_ACCTG_LINE_SYNC”. Select Partner Link as 

SSF_GL_ACCTG_LINE_SYNC.1 and Operation as SSF_GL_ACCTG_LINE_SYNC. 

18. Create Input variable for this activity by clicking Automatically Create Variable buttons. Provide name for 

this variable as shown. 

19. Click Apply and OK on the Invoke activity window. 

Note: There will not be an output variable for this Invoke activity, as this is a one-way consume service on 

BPEL side. 



20. The input to the receiceInput needs to be transformed into the input to the Invoke_getJournalDetails. The 

output from the getJournalDetails DB adapter needs to be transformed into the input to the 

Invoke_SSF_GL_ACCTG_LINE_SYNC. 

21. Drag and drop a Transform activity onto the flow diagram in-between the receiveInput and 

Invoke_getJournalDetails activities. 

22. Edit the transform activity by double clicking it. Change the name to Transform_Input in General Tab. 


a. Source Variable: inputVariable 

b. Target Variable: Invoke_getJournalDetails_InputVariable 

24. Change Mapper file name to Transformation_Input and Click on Create Mapping button to create 




25. Create mapping by dragging and dropping as shown in below. 

26. Save the Tranformation_Input.xsl and close it. Click Apply, OK in the Transform dialog. 

Update Journal Details Transformation 

27. Drag and drop another Transform activity onto the flow diagram in-between the Invoke_getJournalDetails 

and Invoke_SSF_GL_ACCTG_LINE_SYNC activities. 



28. Edit the transform activity by double clicking it. Change the name to Transform_Data in General Tab. 


c. Source Variable: Invoke_getJournalDetails_OutputVariable 

d. Target Variable: Invoke_SSF_GL_ACCTG_LINE_SYNC_InputVariable 

30. Change Mapper file name to Transformation_Data and Click on Create Mapping button to create 


31. Create mapping by dragging and dropping fields as shown below. 



32. Save the Transformation_Data.xsl and close it. Click Apply, OK in the Transform dialog. 



33. Save UPD_JournalDetails.bpel file. Build and deploy UPD_JournalDetails BPEL Process to the default 

domain. This process can be triggered from the BPEL Console. 



REAL-TIME CODE COMBINATION VALIDATION 

Overview 



Process Type 



: Synchronous Two-way 

Real Time Code Combination Validation is a Synchronous BPEL process which can be triggered from any 

Secondary Chartfields page in Campus Solution. It is used to validate the entered Chartfield Combination with the 

combination existing in GL_CODE_COMBINATIONS table of EBS Financials, in real-time. 

When the Real-Time validation is triggered, the message is constructed with: 

1) Ledger Id for which the Secondary Chartfield configuration is done. 

2) Segment Name which is mapped to the Chartfield and 

3) The Chartfield value which will be mapped to Segment Value. 

The Segments values (i.e. Chartfield values) combination will be validated against the combination existing in the 

EBS, by invoking a PL/SQL procedure which will be developed as part of this service. 

The procedure returns a Boolean value based on the validation and this will be propagated back to the Secondary 

chartfields page, from where it was invoked. 

For necessary setups to enable the Real Time validation on the Secondary Chartfield page, please refer 

PeopleBooks. 

The Development of Real-Time Code Combination validation service can be divided into a 2 step process. 

1. Create PLSQL package: Create the PL/SQL package in EBS Financials which handles the validation. 





Step 1: Create PL/SQL package 

The validation of the Code Combination is handled by a PL/SQL package which is created and deployed in the 

EBS Financials database. Following are the details of the Package specification and the body: 

FND_SSF_CF_COMBO_VALIDATION package 

Package Specification 

CREATE OR REPLACE PACKAGE 

apps.fnd_ssf_cf_combo_validation 

AS 

TYPE segarray_rec 

IS 

RECORD 

( 

l_segment VARCHAR2(30), 

l_segment_value VARCHAR2(30)); 

TYPE segarray_tbl 

IS 

TABLE OF SEGARRAY_REC; 

TYPE segment_rec 

IS 

RECORD 

( 

segment VARCHAR2(30), 

segment_num NUMBER(3)); 

TYPE segment_list 

IS 

TABLE OF SEGMENT_REC; 

FUNCTION VALIDATE_SEGMENT_COMBINATION(ledger_id_param IN NUMBER, 

segarray_param IN SEGARRAY_TBL, 

combination_id_param OUT NOCOPY NUMBER) 

RETURN BOOLEAN; 

END fnd_ssf_cf_combo_validation; 

/ 

Package Body 

CREATE OR REPLACE PACKAGE 

BODY apps.fnd_ssf_cf_combo_validation 

AS 

FUNCTION VALIDATE_SEGMENT_COMBINATION (ledger_id_param IN NUMBER, 

segarray_param IN SEGARRAY_TBL, 

combination_id_param OUT NOCOPY NUMBER 

) 

RETURN BOOLEAN AS ret_code BOOLEAN; 

g_segment_list SEGMENT_LIST := SEGMENT_LIST(); 

g_coa_id NUMBER(15); 

s_array fnd_flex_ext.segmentarray; 

BEGIN 

SELECT chart_of_accounts_id 

INTO g_coa_id 

FROM gl_ledgers_public_v gl 

WHERE ledger_id = ledger_id_param; 



FOR l_cur_seg_num IN 

(SELECT fs.application_column_name AS segment, 

fs.segment_num 

AS segment_num 

FROM gl_ledgers_public_v gl, 

fnd_id_flex_segments fs, 

fnd_application fapp 

WHERE fapp.application_short_name = 'SQLGL' 

AND fapp.application_id 

= fs.application_id 

AND fs.id_flex_code 

= 'GL#' 

AND fs.id_flex_num 

= gl.chart_of_accounts_id 

AND fs.enabled_flag 

= 'Y' 

AND gl.mrc_ledger_type_code 'R' 

AND gl.ledger_id 

= ledger_id_param 

ORDER BY segment_num 

) 

LOOP 

g_segment_list.EXTEND; 

g_segment_list (g_segment_list.COUNT).segment := l_cur_seg_nu 

m.segment; 

g_segment_list (g_segment_list.COUNT).segment_num := l_cur_seg_nu 

m.segment_num; 

END LOOP; 

-- 

populate the Segment Array variable which need to be passed as parameter to t 

he get_combination_id routine 

FOR i IN 1.. g_segment_list.COUNT 

LOOP 

FOR j IN 1.. g_segment_list.COUNT 

LOOP 

IF (G_SEGMENT_LIST(i).segment = SEGARRAY_PARAM(j).l_segment) 

THEN 

S_ARRAY(i) 

:= SEGARRAY_PARAM(j).l_segment_v 

alue; 

END IF; 

END LOOP; 

END LOOP; 

-- invoke the get_combinations_id routine 

ret_code := fnd_flex_ext.GET_COMBINATION_ID(application_short_name => 

'SQLGL',key_flex_code => 'GL#', structure_number => g_coa_id,validation_date 

=> SYSDATE, n_segments => g_segment_list.COUNT,segments => s_array, combinat 

ion_id => combination_id_param); 

RETURN ret_code; 

END validate_segment_combination; 

END fnd_ssf_cf_combo_validation; 

/ 





1. Select Applications > New Application Workspace > New Project > BPEL Process Project. 

2. Provide Realtime_CF_Combo_Validation as name and choose Synchronous BPEL Process as type. 

Leave the remaining defaults. Click Next. 

3. Input / Output Elements wizard opens up. Click on Browse to provide the Input and Output XSD 

definitions. The steps to get the respective XSD definitions are explained: 

i) Input schema: 

Navigation: 

Message Name: 



SSF_CF_COMBO_RTVLD_REQ 

VERSION_1 

Go to schema tab to obtain the schema associated with the message. 

This is the schema for the Outbound request message from Campus Solutions which will be used as 

Input schema for the BPEL process. 



Make a local copy of the XSD and point to the XSD from the Input / Output elements wizard. After 

selecting the XSD definition, the user is presented with a Type Chooser wizard. Select the 

SSF_LEDGER_ID element as shown: 

Click Ok. 

ii) 

Output schema: 

Navigation: 

Message Name: 



SSF_CF_COMBO_RTVLD_RESP 

VERSION_1 

Go to schema tab to obtain the schema associated with the message. Make a local copy of the XSD 

and point to the XSD from the Input / Output elements wizard. After selecting the XSD definition, select 

the SSF_CF_COMBO_RTVLD_ITEM element as shown: 



Click Ok. 


5. The designer is presented with an empty Synchronous BPEL process. 

Partner Link Configuration 

6. Double click the client partner link and change the Partner Link name “client” to 

Realtime_CF_Combo_Validation. Verify that the Partner Role and My Role are as shown below. 




Database Adapter (DB Adapter) configuration for invoking the validation routine on EBS 

8. Add a Database adapter from the services palette onto the right swim lane. It opens up an Adapter 

configuration wizard. Click Next to proceed. 

9. Provide Validate_CF_Combination as Service Name and “Validate the Chartfield Combination and return 

1 and Combination Id for a valid combination else 0.” as description. 

10. Select the EBS database connection from the drop down. Click Next. 

11. For the Operation type select Call a Stored Procedure or Function as shown and click Next. 



12. Select the schema from drop down and click on Browse to select the PL/SQL procedure. 

13. Select the package FND_SSF_CF_COMBO_VALIDATION and procedure 

VALIDATE_SEGMENT_COMBINATION as shown: 



14. Click Ok. 






16. Verify the details and click Finish. 

17. Add an Invoke activity after the receiveInput activity and rename it as 

Invoke_Validate_CF_Combination. 

18. Point the Invoke_Validate_CF_Combination invoke activity to Validate_CF_Combination DB adapter. It 

opens up an Edit Invoke dialog. 

19. Auto Create the Input and Output variables as shown: 



20. Add a Transform activity in-between receiveInput and Invoke_Validate_CF_Combination, and rename it 

to Initialize_Params. 



21. Configure the transform activity as described: 

Source Variable: inputVariable 

Source Part: payload 

Target Variable: Invoke_Validate_CF_Combination_CF_Combination_InputVariable (The auto created 

input variable for the invoke activity) 

Target Part: InputParameters 

Mapper File: Assign_Input_2_Params.xsl 

22. Map the Transformation activity as show: 



23. Save the transformation and close it. 

24. Add an Assign activity after the Invoke_Validate_CF_Combination activity and rename it to 

Assign_Output. 

25. Add the following operations to the Assign_Output activity. 

Operation 

type 

From type 


Fragment) 

To type 


XPATH / XML 

Fragment) 

variable="Validate_CF_Combination_Val 

idate_CF_Combination_OutputVariable" 

variable="outputVaria 

ble" 


Copy 

Variable 

part="OutputParameters" 

query="/ns3:OutputParameters/ns3:FND 

_SSF_CF_COMBO_VALIDATION-24V" 

Variable 

query="/ns4:SSF_CF 

_COMBO_RTVLD_IT 

EM/ns4:SSF_CF_CO 

MBO_VALID" 

Copy 

Variable 

variable="Invoke_Validate_CF_Combina 

Variable 

variable="outputVaria 



tion_Validate_CF_Combination_OutputV 

ariable" 

part="OutputParameters" 

query="/ns3:OutputParameters/ns3:COM 

BINATION_ID_PARAM" 

ble" part="payload" 

query="/ns4:SSF_CF 

_COMBO_RTVLD_IT 

EM/ns4:SSF_CF_CO 

MBO_ID" 

26. Save the BPEL process and select the project in the Project Navigator, right click and select to deploy. 

27. Verify that the Process is compiled and deployed successfully without errors. 




28. After the BPEL process is deployed, navigate to the BPEL console and obtain the Endpoint Location for the 

Synchronize Segment values BPEL process as shown: 









2. Search for the Service Operation COMBO_CF_EDIT_REQUEST. 

3. In the General Tab activate the Service Operation by checking the “Active” checkbox as shown. 





Not Required. 


1. Navigate to the Routings tab and Verify that the routing status is set to Active for the Outbound routing 

SSF_CF_COMBO_RTVLD. 


1. Click on the SSF_CF_COMBO_RTVLD routing to change its connection properties. 

2. On the Routings page, go to Connection Properties tab. For the Primary URL field, provide the Endpoint 

Location URL obtained in the BPEL process Design step. 





Not Required. 


Not Required. 



References 

MAPPING 

Below is the mapping used by transformation program. 

SF_ACCTG_LN to GL_INTERFACE mapping 

Oracle GL_INTERFACE 

CS SF_ACCTG_LN 

Column Comments Column 

STATUS 

Value 'NEW' should be 

sent. 

GL_DISTRIB_STATUS 

LEDGER_ID 

Derive Ledger ID based on 

GL Business Unit mapping 

to Ledger, OU and LE (new 

setup) 

BUSINESS_UNIT_GL 

BUSINESS_UNIT 

LEDGER 


ACCOUNTING_DT 

CURRENCY_CODE 

CURRENCY_CD 

DATE_CREATED 

RUN_DT 

CREATED_BY 

Use new field value 

'Created By' setup on the 

GL Business Unit to Oracle 

GL Mapping page. 

ACTUAL_FLAG 

Hard Code to 'A' 


Use the new setup done on 

'Item Classification to 

Journal Category' mapping 

tab in the GL Business 

Unit to Oracle GL Mapping 

page. 



'Journal Source' setup on 

the GL Business Unit to 

Oracle GL Mapping page. 

CURRENCY_CONVERSION_DATE 

ENCUMBRANCE_TYPE_ID 

BUDGET_VERSION_ID 

USER_CURRENCY_CONVERSION_TYPE 

RT_TYPE 

CURRENCY_CONVERSION_RATE 

RATE_MULT 

SEGMENT1 

ACCOUNT 

SEGMENT2 

Column Mapping depends FUND_CODE 

SEGMENT3 

on the new GL BU to 

PROGRAM_CODE 

Oracle GL Mapping 

SEGMENT4 

DEPTID 

Component created to map 

SEGMENT5 

Chartfields to Flexfield 

PROJECT_ID 

SEGMENT6 

Segments 

STATISTICS_CODE 

SEGMENT7 

CLASS_FLD 






SEGMENT8 

AFFILIATE 

SEGMENT9 

BUDGET_REF 

SEGMENT10 

CHARTFIELD1 

SEGMENT11 

CHARTFIELD2 

SEGMENT12 

CHARTFIELD3 

SEGMENT13 

ALTACCT 

SEGMENT14 

OPERATING_UNIT 

SEGMENT15 

PRODUCT 

SEGMENT16 

AFFILIATE_INTRA1 

SEGMENT17 


SEGMENT18 

SEGMENT19 

SEGMENT20 

SEGMENT21 

SEGMENT22 

SEGMENT23 

SEGMENT24 

SEGMENT25 

SEGMENT26 

SEGMENT27 

SEGMENT28 

SEGMENT29 

SEGMENT30 

ENTERED_DR If FOREIGN_AMOUNT > 0 FOREIGN_AMOUNT 

ENTERED_CR If FOREIGN_AMOUNT < 0 FOREIGN_AMOUNT 

ACCOUNTED_DR 

If MONETARY_AMOUNT 

> 0 

MONETARY_AMOUNT 

ACCOUNTED_CR 


< 0 


TRANSACTION_DATE 

Should be NULL - used by 

Journal Import for internal 

processing 

REFERENCE1 

FYI data not used by GL. 

PROCESS_INSTANCE 

Either of the column can be 

SF_GL_RUN_INSTANCE 

used 

REFERENCE2 


REFERENCE3 


processing 

REFERENCE4 

REFERENCE5 

REFERENCE6 

REFERENCE7 

REFERENCE8 

REFERENCE9 

REFERENCE10 

Concatenate the fields and 

insert. This data is FYI and 

not used by GL 

LINE_DESCR 

COMMON_ID 

SA_ID_TYPE 

SF_EXT_ORG_ID 






REFERENCE11 

REFERENCE12 

REFERENCE13 

REFERENCE14 

REFERENCE15 

REFERENCE16 

REFERENCE17 

REFERENCE18 

REFERENCE19 

REFERENCE20 



processing 

REFERENCE21 FYI data not used by GL JRNL_LN_REF 

REFERENCE22 

REFERENCE23 

REFERENCE24 

FYI data to be used to tag 

journal information back to RUN_DT 

CS from GL 

REFERENCE25 

FYI data from Cashiering, 


SF_DEPOSIT_ID 

REFERENCE26 


journal information back to SEQNUM 

CS from GL 

REFERENCE27 


journal information back to SF_LINE_NBR 

CS from GL 

REFERENCE28 FYI data not used by GL JRNL_LN_REF 

REFERENCE29 FYI data not used by GL ITEM_NBR 

REFERENCE30 

Populate with table name - 

SF_ACCTG_LN or 

AV_ACCTG_LN 

JE_BATCH_ID 



processing 

PERIOD_NAME 

JE_HEADER_ID 



processing 

JE_LINE_NUM 



processing 

CHART_OF_ACCOUNTS_ID 



processing 

FUNCTIONAL_CURRENCY_CODE 



processing 






CODE_COMBINATION_ID 

Derive based on the 

Chartfield / Segment 

combination and populate. 

DATE_CREATED_IN_GL 

WARNING_CODE 

STATUS_DESCRIPTION 

STAT_AMOUNT 

GROUP_ID 

REQUEST_ID 

SUBLEDGER_DOC_SEQUENCE_ID 

SUBLEDGER_DOC_SEQUENCE_VALUE 

ATTRIBUTE1 

ATTRIBUTE2 

ATTRIBUTE3 

ATTRIBUTE4 

ATTRIBUTE5 

ATTRIBUTE6 

ATTRIBUTE7 

ATTRIBUTE8 

ATTRIBUTE9 

ATTRIBUTE10 

ATTRIBUTE11 

ATTRIBUTE12 

ATTRIBUTE13 

ATTRIBUTE14 

ATTRIBUTE15 

ATTRIBUTE16 

ATTRIBUTE17 

ATTRIBUTE18 

ATTRIBUTE19 

ATTRIBUTE20 

CONTEXT 

CONTEXT2 

Not stored in SF Tables 



processing 



processing 



processing 

Used by Journal Import 

process. Cross reference 

to the batch process in CS 



processing 



processing 



processing 







INVOICE_DATE 

TAX_CODE 

INVOICE_IDENTIFIER 

INVOICE_AMOUNT 

CONTEXT3 

USSGL_TRANSACTION_CODE 

DESCR_FLEX_ERROR_MESSAGE 



processing 

JGZZ_RECON_REF 

AVERAGE_JOURNAL_FLAG 

ORIGINATING_BAL_SEG_VALUE 

GL_SL_LINK_ID 


SLA for internal processing 

GL_SL_LINK_TABLE 



REFERENCE_DATE 

SET_OF_BOOKS_ID 

BALANCING_SEGMENT_VALUE 



processing 

MANAGEMENT_SEGMENT_VALUE 



processing 

FUNDS_RESERVED_FLAG 



processing 

CODE_COMBINATION_ID_INTERIM 



AV_ACCTG_LN to GL_INTERFACE mapping 


CS AV_ACCTG_LN 


STATUS 

Value 'NEW' should be 

sent 


LEDGER_ID 

Derive Ledger ID based on 

GL Business Unit mapping 

to Ledger, OU and LE (new 

setup) 

BUSINESS_UNIT_GL 

BUSINESS_UNIT 

LEDGER 


ACCOUNTING_DT 

CURRENCY_CODE 

CURRENCY_CD 

DATE_CREATED 

RUN_DT 

CREATED_BY 


'Created By' setup on the 

GL Business Unit to Oracle 

GL Mapping page. 

ACTUAL_FLAG 

Hard Code to 'A' 


Use the new setup done on 

'Item Classification to 

Journal Category' mapping 

tab in the GL Business 

Unit to Oracle GL Mapping 

page. 



'Journal Source' setup on 

the GL Business Unit to 

Oracle GL Mapping page. 

CURRENCY_CONVERSION_DATE 

ENCUMBRANCE_TYPE_ID 

BUDGET_VERSION_ID 

USER_CURRENCY_CONVERSION_TYPE 

RT_TYPE 

CURRENCY_CONVERSION_RATE 

RATE_MULT 

SEGMENT1 

ACCOUNT 

SEGMENT2 

FUND_CODE 

SEGMENT3 

PROGRAM_CODE 

SEGMENT4 

DEPTID 

SEGMENT5 

PROJECT_ID 

SEGMENT6 

Column Mapping depends STATISTICS_CODE 

SEGMENT7 

on the new GL BU to 

CLASS_FLD 

Oracle GL Mapping 

SEGMENT8 

AFFILIATE 

Component created to map 

SEGMENT9 

Chartfields to Flexfield 

BUDGET_REF 

SEGMENT10 

Segments 

CHARTFIELD1 

SEGMENT11 

CHARTFIELD2 

SEGMENT12 

CHARTFIELD3 

SEGMENT13 

ALTACCT 

SEGMENT14 

OPERATING_UNIT 

SEGMENT15 

PRODUCT 






SEGMENT16 


SEGMENT17 


SEGMENT18 

SEGMENT19 

SEGMENT20 

SEGMENT21 

SEGMENT22 

SEGMENT23 

SEGMENT24 

SEGMENT25 

SEGMENT26 

SEGMENT27 

SEGMENT28 

SEGMENT29 

SEGMENT30 

ENTERED_DR If FOREIGN_AMOUNT > 0 FOREIGN_AMOUNT 

ENTERED_CR If FOREIGN_AMOUNT < 0 FOREIGN_AMOUNT 

ACCOUNTED_DR 


> 0 


ACCOUNTED_CR 


< 0 


TRANSACTION_DATE 



processing 

REFERENCE1 


REFERENCE2 

REFERENCE3 



processing 

REFERENCE4 

REFERENCE5 

REFERENCE6 

REFERENCE7 

REFERENCE8 

REFERENCE9 

REFERENCE10 




LINE_DESCR 

EMPLID 

EXT_ORG_ID 

REFERENCE11 

REFERENCE12 

REFERENCE13 

REFERENCE14 

REFERENCE15 

REFERENCE16 

REFERENCE17 

REFERENCE18 

REFERENCE19 

REFERENCE20 

REFERENCE21 



processing 






REFERENCE22 

REFERENCE23 

REFERENCE24 


journal information back in RUN_DT 

CS from GL 

REFERENCE25 

REFERENCE26 


journal information back in SEQNUM 

CS from GL 

REFERENCE27 


journal information back in SF_LINE_NBR 

CS from GL 

REFERENCE28 

AV_BUSINESS_UNIT 

REFERENCE29 

DESIGNATION 


INSTITUTION 


GIFT_NO 


MBR_PMT_NO 

SESSION_NO 

Populate with table name - 

REFERENCE30 

SF_ACCTG_LN or 

AV_ACCTG_LN 


JE_BATCH_ID 


processing 

PERIOD_NAME 


JE_HEADER_ID 


processing 


JE_LINE_NUM 


processing 


CHART_OF_ACCOUNTS_ID 


processing 


FUNCTIONAL_CURRENCY_CODE 


processing 

CODE_COMBINATION_ID 

Derive based on the 

Chartfield / Segment 

combination and populate. 

DATE_CREATED_IN_GL 

WARNING_CODE 

No stored in SF Tables 



processing 



processing 






STATUS_DESCRIPTION 



processing 

STAT_AMOUNT 

GROUP_ID 

Used by Journal Import 

process. Cross reference PROCESS_INSTANCE 

to the batch process in CS 

REQUEST_ID 



processing 

SUBLEDGER_DOC_SEQUENCE_ID 



processing 

SUBLEDGER_DOC_SEQUENCE_VALUE 



processing 

ATTRIBUTE1 

ATTRIBUTE2 

ATTRIBUTE3 

ATTRIBUTE4 

ATTRIBUTE5 

ATTRIBUTE6 

ATTRIBUTE7 

ATTRIBUTE8 

ATTRIBUTE9 

ATTRIBUTE10 

ATTRIBUTE11 

ATTRIBUTE12 

ATTRIBUTE13 

ATTRIBUTE14 

ATTRIBUTE15 

ATTRIBUTE16 

ATTRIBUTE17 

ATTRIBUTE18 

ATTRIBUTE19 

ATTRIBUTE20 

CONTEXT 

CONTEXT2 

INVOICE_DATE 

TAX_CODE 

INVOICE_IDENTIFIER 

INVOICE_AMOUNT 

CONTEXT3 

USSGL_TRANSACTION_CODE 

DESCR_FLEX_ERROR_MESSAGE 



processing 

JGZZ_RECON_REF 

AVERAGE_JOURNAL_FLAG 






ORIGINATING_BAL_SEG_VALUE 

GL_SL_LINK_ID 



GL_SL_LINK_TABLE 



REFERENCE_DATE 

SET_OF_BOOKS_ID 

BALANCING_SEGMENT_VALUE 



processing 

MANAGEMENT_SEGMENT_VALUE 



processing 

FUNDS_RESERVED_FLAG 



processing 

CODE_COMBINATION_ID_INTERIM 

Journal Details mapping from EBS-GL to SF_ACCTG_LN and AV_ACCTG_LN 

Campus Solutions 

ORACLE GL 

SF/AV_ACCTG_LN GL_JE_BATCHES GL_JE_HEADERS GL_JE_LINES GL_PERIODS 

Column Comments Column Column Column Column 

JOURNAL_ID 

JE_HEADER_ID 

JOURNAL_DATE 

DATE_CREATED 

JOURNAL_LINE 

Updated by the Journaling 

Process in Oracle GL 

JE_LINE_NUM 

ACCOUNTING_PERIOD 

PERIOD_NUM 

FISCAL_YEAR 

PERIOD_YEAR 

Updated by the Journaling 

Process in Oracle GL. 


RUN_DT 

SEQNUM 

SF_LINE_NBR 


GL Status - CS Status 

P - D 

U - G 

Other values - N 

No update occurs - used only for 

reference and tracking 

GROUP_ID 

STATUS 

REFERENCE_4 

REFERENCE_6 

REFERENCE_7 

This column contains the table 

name 

(SF_ACCTG_LN/AV_ACCTG_LN) 

to which this record should be 

updated. 

REFERENCE_10 



XSD SCHEMA 

Following is the SSF_ACCTG_LINE_TRFM_EBGL schema definition 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


type="NUMBER"/>

Campus Solutions 9.0 to EBS Financials (General Ledger ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?