What is the Significance of Using GB_QRY_LINK_VW in Group Build?
(Doc ID 1549697.1)
Last updated on APRIL 20, 2023
Applies to:
PeopleSoft Enterprise HCM Human Resources - Version 9.1 to 9.2 [Release 9]Information in this document applies to any platform.
Goal
Group Build works fine without GB_QRY_LINK_VW.
Scenario ---- if multiple rows returned for a Custom Query ---
The issue can be reproduced at will with the following steps:
1) Create a PSQuery in Application Designer and review result count.
2) Use this same PSQuery in a Group Build Definition.
Navigation: Set Up HCM > Common Definitions > Group Build
3) Click on the icon on the Group Build Definition page to show the count result.
Notice the count from the PSQuery does not match the count result in the Group Build Definition.
In PeopleBooks "PeopleSoft HCM 9.1 Application Fundamentals PeopleBook" navigation "Home > PeopleBooks > PeopleSoft HCM 9.1 Application Fundamentals PeopleBook > Setting Up and Working with Group Definitions," it states:
When you define a query to use in group definitions, the following rules apply:
The first record you insert into the query must be the Group Build view (GB_QRY_LINK_VW).
The system uses this view to merge SQL statements that are created in the Group Build pages with the SQL statements that are created by PeopleSoft Query.
However, it seems that Group Build work fine if this view is excluded, as long as JOB record is part of the query definition. What is the significance of using GB_QRY_LINK_VW and what negative interactions might result in using JOB and not this GB view?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |