When Peoplebooks Is Not Enough
Archive for the ‘Peoplesoft Specific’ Category.
We’re always happy yet apprehensive to get a new bundle of bug fixes for Peoplesoft. We anticipate that our applications will run more reliably, perhaps faster, and maybe with a few new features. The chore that nobody likes, though, is checking for Oracle’s changes that affect the Peopletools objects we have customized.
Continue reading ‘Merging Bundles With Customized Peopletools Objects’ »
I have nothing against subqueries, but there are times in the Peoplesoft environment that they are unnecessary. If we can get exactly the same results with simpler, faster SQL, let’s avoid subqueries.
Continue reading ‘Avoid Subqueries’ »
Some organizations manage their workforces with positions. A position specifies a job and a place on an organization chart, which can exist without a person or with more than one person. Position management can give organizations more control over their structures, budgeting, and succession planning.
Continue reading ‘Views You Can Use: Position Data’ »
Peoplesoft HCM has tens of thousands of record definitions, representing tables, views, and other Peopletools objects. Nonetheless, we can find more ways to organize our data usefully for easy access in Query Manager or in database browsers like SQLPlus and TOAD. This is the first of an occasional series of posts regarding new ways to access our data. This week: PS_LEAVE_ACCRUAL.
Continue reading ‘Views You Can Use: Leave Accrual’ »
What is the relationship between SQR and Application Engine? Is one better or are they complementary? They are both frameworks for batch processing in the Peoplesoft environment. As such, they must have overlapping functionality. Like Star Trek and Star Wars, they each have fans and detractors, with not always rational reasons for their preferences.
Continue reading ‘SQR Versus Application Engine’ »
Peoplesoft HCM (HR, BA, PR, and TL) comes with at least 1300 run control records, yet my organization has added 2% more over the past ten years. We’re not running out of table space or disk space, but we probably did more work than we needed; creating new records, tables, and pages. For that matter, Oracle probably did more work than they needed, not reusing their run control objects.
Continue reading ‘Re-Use Peopletools Run Control Objects’ »
Last week, we considered change reporting based on the effective dates and action dates of PS_JOB. Other Peoplesoft tables track history differently. We need other approaches to report those changes.
Continue reading ‘Reporting Changes In Peoplesoft With SQR, Part 2’ »
Most of my report and interface programs output snapshots of the database. Reports and interfaces about how the data has changed are more challenging. The effective date model of many Peoplesoft tables suggest that we can easily extract the history of data, but the difference between effective dates and action dates, and the availability of correction mode complicate the issue.
Continue reading ‘Reporting Changes In Peoplesoft With SQR, Part 1’ »
The only aspect of an SQR program that must be unique is its file name. The file name may also indicate something about the program within. There are restrictions on SQR program file names in the Peoplesoft environment, but there’s more flexibility than meets the eye. Continue reading ‘SQR Program File Names’ »
It is refreshing to have a new copy of the production database instance in the development database instance. It is also a bit frightening. Was anything important lost in the overwrite? Continue reading ‘Never Fear A Database Refresh Again’ »