HOME · FORUMS · ABOUT · LINKS · CONTACT US  
ABOUT PEOPLESOFT
What is PeopleSoft?
PeopleSoft Q & A
PeopleSoft&Oracle
Who is Larry Ellison?
PeopleSoft Modules
Oracle Modules
PeopleSoft 9
Project Fusion
 
TOOLS & TRAINING
Developer Tools
Consulting Tools
PeopleSoft Training
PeopleSoft Connect
Project Management
 
CONSULTING
Consulting Firms
Consulting Reviews
 
JOBS
PeopleSoft Jobs
Immigration (H1-B's)
 
OTHER LINKS
Forums
PeopleSoft News
Interviews
PS Gossip
Your Feedback
Friends of the Planet
Editors Blog
 

PSPlanetXpress
Newsletter

Please note that all fields followed by an asterisk must be filled in.

First Name*
E-mail Address*

Your e-mail address is secure. We will only use it to send you PeopleSoft-Planet related bulletins and information.

 
 

 

  Frequently Asked Questions (FAQ's)


 

Summary:
I am having a problem with interactive versions. I need to show and hide certain columns depending on versions. I am using SL VersionName to solve this, but the problem is that the value in SL VersionName is the same for all versions. Does anyone have any suggestions?

Answer1

To show or hide columns depending upon versions, you should have a Processing Option attached to the Report. You can have an item in the Processing Option for this purpose and based on the PO value you can hide/show the columns.

Answer2

There is another workaround I have used successfully without having to change the Processing Options template. It's not elegant, but it works. Try this:

Create one or more custom UDC tables to store your version and the flags you need, and read them during the Dialog is Initialized or Post Dialog is Initialized event at runtime.

For example:
I used UDC table 58/P1 to store a flag to display or not display certain form controls on the application:
Code Description 1 Special Handling
IAA0001 Display date columns 1
IAA0002 No date display 0

Then during the Dialog is Initialized event, I added code to get the Special Handling Code from the UDC table using the N0800031 Business Function N0800031. I used the SL VersionName to pass into the Business Function, then used the output to hide or show the columns as applicable.

Answer3

It will be difficult to handle this situation if you don't use the PO template for handling different versions. There are other ways to do it, though. If you know the situations where a particular version is used, then by specifing that situation flag you can hide or show columns with different versions.

*Questions excerpted from ITToolBox.com*

Disclaimer: Contents are not reviewed for correctness and are not endorsed or recommended by PeopleSoft-Planet.com.

 SPONSORED LINKS


 

FIVE PILLAR CLUB


PeopleSoft-Planet.com is a  FIVE Pillar member site.

read more

OPTIONS

Give us your feedback

Send us your resume

Add to your favorites

Make your home page

To recommend this site to a friend, enter their email address

and then hit button to:

BOOKSTORE


Our r
ecommended reading this month is Understanding PeopleSoft 8 by Lynn Anderson

More Books

 
 

Barebones at the lowest prices



 
Trademarks referenced on the PeopleSoft-Planet website are property of their respective owners. Comments are property of their respective posters.
PeopleSoft-Planet is brought to you by Nnigma Inc. Web site code is Copyright © 2005 by Nnigma. All Rights Reserved.