Skip navigation

The FMS Expenses team has started a new MOS Community initiative: Tip of the Week.


Check out the 3 Tips already posted and share in the discussions:


- Tip Of The Week : Full Data Publish Utility - Configurable Full Sync :


- Tip Of the Week : Tables Accessed and Updated Report – An Easy Way to Find Out Which Records are Accessed During a Process Run :


- Tip Of the Week : Find Object Navigation Utility – An Easy Way to Find Out the PIA Navigation of a Portal Object :


Explore, Enjoy & Share Your Experiences!

The Affordable Care Act is a huge initiative. One big piece of the legislation that has been evolving is Employer Shared Responsibility. PeopleSoft has already delivered some new functionality to assist with the Employer Shared Responsibility requirements. Part of delivered functionality was an Excel to Component Interface. The Excel to CI will allow you to quickly and easily upload key ACA employee information to PeopleSoft. PeopleSoft has scheduled a live Advisor Webcast for Wednesday, June 24, 2015 10:00 AM (PST) to go over the delivered functionality and show users how it works.


Register for this webcast on My Oracle Support Document ID 1456265.1.

EX Expense Report Approval on 9.2 DEMO DB


Pere Taulé


PeopleSoft Enterprise FSCM 8.9, FSCM 9.0, FSCM 9.1, and FSCM 9.2 versions make use of the Approval Workflow Engine (AWE) tool to manage and process Approvals from all Expense transactions: Expense Reports, Cash Advances, Time Reports, and Travel Authorizations.

The EX team completed a full test in the Support DEMO DB FSCM 9.2 Image #12 GCS Environment, and compiled all screenshots on technical configuration, system delivered data, functional settings and more!

    • First and foremost, the best source of information on Expenses Approval Workflow is PeopleBooks. It contains all explanations needed to understand all the different parts, how to configure them, and the impact, and relation they have with the rest of the delivered functionality. Please, click the link to the PeopleSoft Enterprise FSCM 9.2 Expenses PeopleBooks: Understanding Setting Up Approvals and Audit Rules.


    • Additionally, the below listed Knowledge Management Document was created to clarify the Expenses Approval Workflow from Application Release FSCM 8.9 onwards. Special attention was paid to the technical configuration, the settings with system delivered data, as well as functional set up depending on the customer's requirements. Some examples were provided in terms of Word documents in various FSCM Versions. Recently, FSCM 9.2 information have been updated.
    • [ Note 650548.1 ] - EEX8.9+: How does the Expenses Approval Workflow work and is setup in FSCM 8.9, 9.0, 9.1, and 9.2?


  • Finally, a full test has been completed in our FSCM 9.2 Image #12 GCS Environment, and all screenshots were compiled on technical configuration, system delivered data, and functional settings. Please find here below attached the PDF file containing all the information.


Comprehensive Step by Step details in [ Note 1525252.1 ] attached PDF. Due to focus on screen prints/shots, it is recommended to increase the zoom level to 150-200% for clarity.

Upgrade challenge: Can you get there from here?

Staying on a supported platform


Upgrade Goal:

          You need to have both the Source and Target environments installed on the same supported platform.

          This is how upgrades are written by Oracle/PeopleSoft, and how they are tested and supported.


Problem:  The new-codeline environment, the Source, is not supported on the platform where the Target is installed.

           And vice versa.   What to do?


Solution:   Find the happy medium platform where both Source and Target environments can be supported.

          This may not be the desired platform you want to end up on. But after the upgrade is completed,

          you can fine tune the environment to be the platform originally wanted.


Here's an example: 


The current production environment is FSCM 9.1, using PeopleTools 8.52.09, on Msft Sql Server 2008 R2 on a Windows 2008 R2 64-bit server.


The goal is to upgrade to FSCM 9.2, using PeopleTools 8.54.xx, on Msft Sql Server 2014 on a Windows 2012 R2 64-bit server.


What would be an upgrade path that will allow both the Source and Target to be installed on a certified platform?

And, by the way,  how does PUM come into the picture?


The challenge is that an environment built with PeopleTools 8.52 is not supported on Msft Sql Server 2014; and an environment built with PeopleTools 8.54 is not supported on Msft Sql Server 2008.

But both PT8.52 and PT8.54 are supported to use Msft Sql Server 2012 on a Windows 2008 R2 64-bit server.

This will be the in-between step to allow both environments to be installed on a certified plaform during the upgrade.


To prepare for the PeopleSoft upgrade, first transition the Msft Sql Server 2008 database to Msft Sql Server 2012.

The FSCM 9.1 / PT 8.52 is will then be on Msft Sql Server 2012 on the Windows 2008 R2 server.


Install the FSCM 9.2 / PT 8.54.01+ on the Msft Sql Server 2012 on the Windows 2008 R2 server.


Perform the upgrade, then as a final step, transition the Msft Sql Server 2012 database to Msft Sql Server 2014, on a Windows 2012 R2 server.



     Finding a happy medium rdbms release where both Source and Target are supported


Upgrade available:  go further


The upgrade from FSCM 9.1 to 9.2 image 11 is now available.   See document PeopleSoft Financials and Supply Chain Management Upgrade Home Page (Doc ID 1963697.2).  This upgrade would allow you to end up on 9.2 release with all maintenance and new features included through image 11.


The Source environment can be installed in the classic manner, using virtual cds from the Software Delivery Cloud (previously called e-delivery) which are packaged at the FSCM 9.2 image 11 release.


Did you say PUM?


Or, optionally, the Source environment can be installed from a PUM Source Image  -- if the environments are English-only and the upgrade is to be English-only.   [This requirement may change for future upgrade paths.]  See the PeopleSoft Upgrade Source Images Home Page (Doc ID 1552580.1) to obtain the FSCM 9.2 image 11 Upgrade Source Image.  


Note that for this upgrade, the minimum PeopleTools release is PT 8.54.08.


What about required-for-upgrade patches?


Regardless if the Upgrade Source image is used, or if the Source is installed from virtual cds, the required-for-upgrade patches already included are only up to the release level of Image 11.  There is now available a FSCM 9.2 Image 12.  Download the Update Image 12, and apply any required-for-upgrade patches from that image to the Source environment. 


Note that applying all maintenance from the Image 12 does not make the upgrade FSCM 9.1 to 9.2 Image 12. Only apply required-for-upgrade patches from the Update Image 12, in order to be most successful in the upgrade.


PUM is part of the upgrade picture as of PeopleTools 8.53 and onwards.  It is part of getting ready for the upgrades to application release 9.2.



Come to Support Central and join us for OHUG Jeopardy.  Show off your knowledge of MOS, OHUG, and our MOS Communities and win great prizes.  We'll be playing at 10:15 and 3:15.

Great audience!





Come see Oracle Support engineers & managers in Support Central.  Play OHUG Jeopardy for fun prizes.


Today is SIG/RUG day at OHUG.  Opening reception is this evening.  See you at Support Central starting tomorrow.  Come play OHUG Jeopardy with us!

A comprehensive Knowledge document (Document 1969707.1) on FSCM 9.2 Fluid Mobile Approvals is available! The KM document contains a Word attachment, called "Fluid Mobile Approvals Setup FSCM," with screenshots of all setup required for eProcurement, Expense, Payables, and Purchasing applications and it also addressing some packaging issues.


The areas covered in the this document are:

1. Gateway Configuration

2. Web Service and REST Service Target Locations

3. Portal Default Local NodeMobile Approvals.bmp

4. Verifying the Domain Status

5. Activating Services

6. Introspection and Deployment of Services to Local Node

7. MAP Layouts Permissions

8. Synch the MAP Details for Web Server

9. Mobile Approval Options


In this document you will also find links to other important documentation, such as the Mobile Installation document 1990593.1, and videos to assist you further with Fluid Mobile Approvals. 

Have you been running out of memory when processing letters through CommGen?  If the process is grinding along but too slowly, or if the process fails altogether, you may be running into a recently discovered bug for which we have a workaround.  You may also be able to improve processing speed by employing a technique to significantly reduce the graphics load in your document.


First, let's talk about the bug. Bug 20423942 has been reported to Development because garbage collection hasn't been handled well during the process.  Sometimes there may be unrecoverable application objects that can no longer be referenced from PeopleCode, but which have not been reclaimed and so are still taking up computer memory. The CollectGarbage() function is automatically invoked by the application server as part of its end-of-service processing, so generally it is not necessary to call it for online applications. However, in Application Engine it is possible that a long-running batch job could grow in memory usage over time as these unreferencable Application Objects accumulate. The problem identified in the bug is that we only call the garbage collector once, rather than periodically, to reclaim these objects.


If you'd like to overcome the problem that this causes for you, you can add "CollectGarbage()" to a specific location in the SCC_COMMGEN AppEngine. You can read more about this workaround in SCC_COMMGEN Memory Consumption Issues (Doc ID 2015485.1).


Even if you aren't having this problem, or have already overcome it, you can improve processing by reviewing the way that you handle logos and other graphics in your letters.  If you are using MicroSoft Word for your letters and include a logo, you may be running the process with a graphic that can be significantly reduced in size.  Word by default will include the graphic as an .rtf file, but if you save the letter as an html file Word will also save a form of the graphic in another folder as a .png and .gif.  These are much smaller in size and by substituting them for your current image you can improve performance rather substantially.  Take a look at SCC_COMMGEN Memory Consumption Issues due to TEMPLATE SIZE (Doc ID 2015496.1) to find out how to do this.   

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see for instructions.