EGL: Enhancements For Business Request Template (Doc ID 2122692.1)

Last updated on FEBRUARY 15, 2017

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Goal

The following enhancement requests are needed for the Business Request Template:

1. Allow rows in each template section to be modified or deleted after the template has been used.

Navigate to Setup FSCM -> Common Definitions >Business Request Configuration -> Business Request Template and add a new template for Account and save it.
Navigate to Setup FSCM -> Common Definitions >Design Chartfields > Define Values > Chartfield Request and add a new request for field name Account.
Submit it for approval.
Next navigate back to Setup FSCM -> Common Definitions >Business Request Configuration -> Business Request Template and open the template for Account that was initially setup. Everything is grayed out and we are not able to change anything. The system does not have a feature to add effdt to the template. Once used there is no way of making any changes.

2. Allow more than one date option in each template section.

When setting up a Business Request Template, in the Tree section, it is not useful to have only 1 date defined. The Business request would be used over many months so any newly eff dated trees would not be the ones that get updated with the business request. For example, it you use 1/1/1900 but at some point in the future create a newly eff dated tree with a 6/1/15 date, you would not want the 1/1/1900 tree to continue to be updated.

For example: I have 2 different Account reporting trees, one for SEC reporting, one for FERC reporting as these 2 agencies treat some accounts differently.

If I set up a Business Request Template for adding of new accounts, when I initially define the template I will use the most current tree, which in my example, would be dated 1/1/2016. If I have to add a new account in March, 2016, for example, I will create 2 newly eff dated trees also dated 3/1/2016. As soon as I do that, I would have to go update the Business request Template to now point to the 3/1/2016 trees, and I would have to keep doing that every time I added new accounts. This pretty much negates all the efficiency I gained by using the Business request in the first place. If I could have an option to NOT populate the eff date on the Template, but instead use something like "Most recent effective dated tree" that would be better.


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms