Application Data Set that You might be Needing - Questionnaire Framework ADS

Posted on

Introduction

    Before we dive into the actual content, if you are not already familiar with Application Data Sets (ADS), I strongly suggest you review my earlier blog, Application Data Sets – All-in-One Guide*](link), and the PeopleTools 8.62 PeopleBook.
    While ADS provides great flexibility for Business Analysts and Application Administrators to set up definitions for moving configuration data between application instances, not all the definitions you might expect are currently available. Oracle’s PeopleSoft application team continues to add new ADS definitions with every Tools and Application PUM release.
    In this blog, I’m going to talk about an ADS definition I created based on a Support Community discussion that started back in 2022.

Note: The number of available ADS definitions may vary depending on your application - FSCM, HCM, or CS.

Background

    This was initially brought up by a community member, Jun Deguchi, who wanted to share valuable information after an extensive search (see Doc ID 2731569.1) on exporting and importing Questionnaire Framework data.
    At first, I thought, “Okay, maybe in the last two or three years Oracle would have delivered this.” To my surprise, even with Tools version 8.63, it was still not available (I checked). So, I decided to create it myself and share it with the community so that no one else would face the same difficulty Jun Deguchi experienced in 2022.

How It’s Done

The Questionnaire Framework setup is divided into four or five major areas:
  1. Categories
  2. Questions
  3. Answers
  4. Smart Answers
  5. The Questionnaire itself
    I created a separate ADS definition for each area so they can be optionally selected and included in an ADS project during Data Migration Workbench activities.
    The relationship between these ADS definitions is straightforward, based on key mappings. You can think of it as a flow from Categories → Questions/Answers → Questionnaire.

Fig. 1: Created ADS Definitions

    The related records were added according to their parent-child relationships, and the connections between ADS definitions were defined on the Relations page.
Fig. 2: ADS Definition - General Page

Fig. 3: ADS Definition - Relations

For data integrity, I included the following relation properties:
  • Insert into Project – When inserting a “From Data Set” instance into a project, optionally insert related “To Data Set” instances.  
    • Setting: Optional Insert
  • Validate Relation – Verify all required “To Data Set” instances exist for all “From Data Set” instances in the project.  
    • Setting: Error
Basic properties were also assigned accordingly.

Fig. 4: ADS Definition - Properties

Conclusion

    With this setup, you can save significant time when moving Questionnaire Framework configurations between instances—from Development to TEST, QA, UAT, or others.  
All you need to do is:
  1. Download the App Designer project from GitHub PeopleSoft Samples – BD_EOQF_ADS_PRJ_MV.zip.
  2. Import it via Application Designer into your Development instance.
  3. Use Data Migration Workbench (DMW) as usual to migrate your Questionnaire Framework data.
I’ve already validated this by performing an export and import—and it worked perfectly.

Fig. 5: Import ADS Project from File

Don’t wait - download and use it, and let me know your feedback when you can.

Happy Helping! 😃
Matheshwaran V
Labels =>
Location: Coimbatore, Tamil Nadu, India

Comments

Post a Comment

You might wanna check out my Popular Post

Running Connected Query BIP / XMLP through Peoplecode / AE Process

Posted on
Hi All, Most of us tend to find the Answer for this Question "How to I execute Connected Query XMLP report through Peoplecode or AE Peoplecode?" Here it is, what you are seeking for, import PSXP_RPTDEFNMANAGER:ReportDefn; import PT_CONQRS:QUERYITEMPROMPT:*;  import PT_CONQRS:CONQRSMGR:*;  Global string &BU, &Invoice;  Local array of PT_CONQRS:QUERYITEMPROMPT &prompts;  Local File &xmlFile; &reportDefinition = "XX_CONNQRY";  &connQueryName = "BI_INV_PRNT_CQRY_V1";  /* Start by creating the Connected Query Object */  &connQueryObject = create PT_CONQRS:CONQRSMGR("", &connQueryName);  If Not (&connQueryObject.Open( False)) Then  /* If it can't be opened, throw an error */   Error ("Failed to open Connected Query.");  End-If; If Not (&connQueryObject.Validate()) Then  /* Validate that all PSQueries within the Connected Query Exist */   Error ("Unable ...
Read more

Localize your PeopleSoft System Date

Posted on
In Peoplesoft system you can easily localize your Date format based on your country format. For that what you need to do is Log on to PIA (Pure Internet Architecture) through the User ID has PTPT1000 Permission List Go to Root >> PeopleTools >> Personalization >> Locale Defaults Search for your PIA's default language code (e.g.: "en-us") For user option "Date Format" change the "Override Value" to  D for DDMMYY format M for MMDDYY format Y for YYMMDD format Note YY or YYYY is based on Page Field properties Also for "Date Separator" you can use any Single Character to separate / (Forward Slash) is a default one Save the Page Now where ever the Date field is occurring which will appear in the updated format. and this can be overridden by Users personalization which is in, My Personalizations >> Regional Settings and change the Date Format and Date Separator options based on your convenience....
Read more