I shouldn’t claim that this bug appears in every SQR program written for the Peoplesoft environment. It’s not even in every SQR program that takes run control parameters. But I bet it is in most of them.
Archive for the ‘Peoplesoft Specific’ Category.
Last week we discussed finding the best Peoplesoft page, and the menu path to that page, for viewing and updating a particular database table. We have a similar need to find the menu path to the run control page for a particular batch process.
Continue reading ‘From Process To Peoplesoft Page’ »
When I discuss data with my colleagues in the Human Resources and Payroll departments, we speak different languages. I talk about tables and columns. They talk about menus, tabs, and pages. “You need to change EEO4CODE in PS_JOBCODE_TBL,” I’ll say. They’ll reply, “You mean, select Setup HRMS, Foundation Tables, Job Attributes, Job Code Table, and the Job Code Profile tab?” There are pages I’ve never visited and they’ve never used a SQL browser.
Continue reading ‘From Database Table To Peoplesoft Page’ »
PS_EMPLOYMENT used to be a SQL table. Now it is a SQL view that joins PS_PER_ORG_ASGN, PS_PER_ORG_INST, and PS_JOB. Of course, PS_JOB has two subselects to pick a single value of EFFDT and EFFSEQ for each value of EMPL_RCD. The subselect for EFFDT is unusual and it may not behave the way the designers intended.
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’ »