Search This Blog

Showing posts with label others. Show all posts
Showing posts with label others. Show all posts

e-learnings - a functional point

PAY_ONE_TIME - You would have heard about this table for making adjustments after pay run first calc. Point is, if you are adjusting by (an app engine for example) process, the adjustment entries may be not of PAY_CHECK's. Technically what I am trying to say is, "When you are making entries into PAY_ONE_TIME, dont join PAY_CHECK, just join PAY_EARNINGS with SINGLE_CHECK_USE in P or N. The Pay Calc will take care of pulling it off in Paycheck".

OriginalValue

This property returns the value of a field, that is, the value that from the database. If the value hasn't been changed and saved by the user, it is the original value from the database. If the value has been changed and saved by the user, it is the existing value in the database. This property does not work for derived records. Original values are the database values, and derived records do not have a corresponding database value.

Example

&Orig = &MyField.OriginalValue;

If &Orig = &Date Then

/* do current day processing */

Else

/* do other processing */

End-If;


 

How PeopleCode Programs are Stored and Saved

When you save an Application Designer definition, PeopleTools saves all PeopleCode programs belonging to that definition that have been added or modified. Component record field PeopleCode and component record PeopleCode belong to the component. If new PeopleCode programs have been added, PeopleTools creates an association between the owning definition and new rows in the PeopleCode table. If a PeopleCode program is deleted, the association between the owning definition and the program is also deleted.

Saving PeopleCode programs together with their owning definitions helps to guarantee the integrity of the application. In the event of system failure, it’s now extremely unlikely that your application could end up storing PeopleCode programs that are not associated with any definition; or worse, a definition associated with a PeopleCode program that was never saved.

When you save any Application Designer definition, all PeopleCode programs that you’ve added or changed since the last save will be checked, formatted, and saved at the same time.If you want to format and check the syntax of a single PeopleCode program, use the Validate Syntax command instead of the Save command.

Automatic Backup of PeopleCode:

A PeopleCode program is automatically saved to a file while you’re working on it. This checkpoint occurs at the following times:

·       Every 10 keystrokes.

·       On a save command, just prior to the save being executed (in case the save doesn’t actually

execute because the code is invalid).

·       When another PeopleCode program is selected to be edited (if you have two PeopleCode editor

windows open at the same time, and you move from one to the other).

The file is saved to your temp directory (as specified in your environment), in a file with the following name:

PPCMMDDYY_HHMMSS.txt where MMDDYY represents the month, date and year, respectively, of the checkpoint, and HHMMSS represents the hour, minute and second, respectively.

The top of the checkpoint file contains the following information:

[PeopleCode Checkpoint File]

[RECORD.recordname.FIELD.fieldname.METHOD.eventname]

If your PeopleCode program is saved successfully, any checkpoint files associated with that program are automatically deleted.

Refresh the Events list


  

Indexing processes in TAM module

The key word search in the in the Job search page was not working properly was the issue raised by the customer. The search was working fine in the development instance. People Book search revealed the fact that there are processes which will index the active job postings for the search. we ran those processes and the Keyword search was working fine. These processes, which were scheduled in the production environment was failing because of some issues, which created the whole issue.

However the identification of the processes are added into the learning collection. Those processes are given below.

Build Job Index
Run the process to build or rebuild the Verity index of jobs.

Build Applicant Index
Run the process to build or rebuild the Verity index of applicants.

Run Job Search Agent
Run the Job Search Agent process.

Jolt Pooling issue fix

If you have read my previous post on Web Server Jolt Pooling & Download to Excel relation, here are some more information I just received from my Data base administrator.

While the Jolt Pooling feature is introduced, it was an efficient way to balance the load to the application server. However the limitations made the roll back of the feature. That is why the 'Disabling of Jolt Pooling' helped to solve the issues regarding the Excel download and View attachment functionality.

Now the fix for the issues while Jolt Pooling is enabled, is released by Oracle. Thanks to my DBA for providing this valuable information.

From Customer connection

SOLUTION  201036989 - E-FTP: ViewAttachment does not work after upgrade to tools 8.48.xx.

SPECIFIC TO:
Enterprise PeopleTools 8.48.xx

ISSUE:
ViewAttachment does not work after upgrade to tools 8.48.xx. View attachment does not work on first click but does work on second or third attempt.
Tools 8.48 has change in web.xml file for Jolt Session Pooling.
Jolt Session Pooling is set to True by default, which was not the case in earlier tools release.

SOLUTION:
This seems to be only affecting PT 8.48 and greater releases at this point. Please see workaround to resolve this issue.
The final fix for this issue is in tools patch 8.48.16 and 8.49.09, where Joltpooling is not required to be disabled for Viewattachment.

WORKAROUND:
Change the web.xml file as follows.
init-param>
<param-name>joltPooling</param-name>
<param-value>false</param-value>
File should be in following directory    
./applications/peoplesoft/PORTAL/WEB-INF/web.xml
There are several servlet where joltpooling is enabled, you need to change only for PSP and PSC servlet.
Also you need to bounce the web server and delete web server cache.

Two and Three tier connections

What is a 2 tier connection?

Well, In general, the user system interface client invokes services from the database management server. In many two tier designs, most of the application portion of processing is in the client environment.

The database management server usually provides the portion of the processing related to accessing data (often implemented in store procedures). Clients commonly communicate with the server through SQL statements or a call-level interface.

It should be noted that connectivity between tiers can be dynamically changed depending upon the user's request for data and services.

Webopedia states "Refers to client/server architectures in which the user interface runs on the client and the database is stored on the server. The actual application logic can run on either the client or the server."

One of the disadvantages of a two tier setup is performance.

For instance, suppose you get a sudden flood of requests coming in. Your web server might be able to handle the number of incoming connections, but now, since all of the non-DB processing is happening on the same machine, you become CPU-bound, so that, even though the web server can accept more connections, it can't get enough of the CPU to service all of the requests it has.

What is a 3 tier connection?

A 3-tier application is an application program that is organized into three major parts, each of which is distributed to a different place or places in a network. The three parts are:

In a typical 3-tier application, the application user's workstation contains the programming that provides the graphical user interface (GUI) and application-specific entry forms or interactive windows. (Some data that is local or unique for the workstation user is also kept on the local hard disk.)

Business logic is located on a local area network (LAN) server or other shared computer. The business logic acts as the server for client requests from workstations. In turn, it determines what data is needed (and where it is located) and acts as a client in relation to a third tier of programming that might be located on a mainframe computer.

The third tier includes the database and a program to manage read and write access to it. While the organization of an application can be more complicated than this, the 3-tier view is a convenient way to think about the parts in a large-scale program.

A 3-tier application uses the client/server computing model. With three tiers or parts, each part can be developed concurrently by different team of programmers coding in different languages from the other tier developers.

Because the programming for a tier can be changed or relocated without affecting the other tiers, the 3-tier model makes it easier for an enterprise or software packager to continually evolve an application as new needs and opportunities arise.

Existing applications or critical parts can be permanently or temporarily retained and encapsulated within the new tier of which it becomes a component.


 


 

Special Actions

There are certain action in HRMS which can make the Inactive rows in the Job data active. Identification of these Actions will be helpful while development phase. Below is the query to identify those actions.


 

SELECT

A.ACTION

, A.ACTION_DESCR

FROM

PS_ACTION_TBL A

, PS_ACTION_STAT_TBL B

WHERE A.ACTION=B.ACTION

AND A.EFF_STATUS='A'

AND A.EFFDT= (SELECT
MAX (C.EFFDT)

FROM PS_ACTION_TBL C
WHERE A.ACTION=C.ACTION)

AND B.HR_STATUS_VALID='I'

The setting is done under
Setup HRMS
Product related
Workforce Administration
Actions

Here under the Organizational Relationship scroll, there is field
'Valid if Previous HR Status is: '. Providing Inactive will make
the action capable of
changing the inactive HR status active

Running Application Designer on Linux

One of the requests for enhancements in the PeopleTools Product Strategy group on Oracle Mix is for the ability to run Application Designer on Linux. This was actually discussed in the session that the PeopleTools Product Strategy group hosted at Oracle OpenWorld this year.

Although most people think it's not possible, read on and see that you
can have an Application Designer icon on your Linux desktop that works just like Windows. But first, a bit of relevant history.

Read More…

Private Cloud: A Natural Evolution for Enterprises


Cloud computing has been enjoying a splash of media attention. But what IS the cloud? And how can your enterprise get its benefits without the risks?

Cloud computing is a relatively new term for computing platforms that provide flexible, scalable resources that are accessed over a network. Cloud computing offers a powerful, highly efficient, and flexible service to business users, who can tailor it to their requirements without needing to know anything about the underlying technology.

There are many "public" cloud computing services, such as Google App Engine and Amazon EC2, that offer businesses a way to create and access applications with no infrastructure setup, minimal management, and low up-front costs. The challenges of these public cloud services can become evident, however, when you attempt to integrate them with other applications in your infrastructure, or when you need to keep tight control of your data or quality of service.

Cloud Inside the Firewall
With a long history of grid computing expertise and the industry's most complete and integrated middleware, Oracle offers IT departments the ability to provide the benefits of a cloud—elastic computing capacity and self-service deployment—as a private or internal service, avoiding some of the downsides of a public cloud.

"A private cloud is a natural, evolutionary step for the enterprise," says Alex Andrianopoulos, vice president of product marketing for Oracle Fusion Middleware, Oracle. "Using an integrated set of Oracle technologies, an IT team can provide the departments and divisions throughout an enterprise with a platform that delivers all the advantages  of cloud computing, but allows them greater freedom to integrate current resources and control quality and security."

A platform-as-a-service (PaaS) private cloud is an architecture for centralized, shared resources, internal to the enterprise, that allows departments to rapidly deploy and easily manage applications. The following Oracle Fusion Middleware technologies make it possible:

  • Application grid is a foundation architecture that provides the dynamic resource adjustment that gives PaaS cloud computing its elastic qualities. Application grid leverages the capabilities of several Oracle Fusion Middleware components, including Oracle WebLogic Server, the world's No. 1 application server; Oracle Coherence, the industry's premier in-memory data grid; Oracle Tuxedo, the industry's No. 1 distributed transaction processing platform; and Oracle JRockit, the world's fastest Java runtime.
  • Oracle SOA Suite and Oracle Business Process Management Suite allow developers to build and orchestrate reusable services and components, so business users can quickly assemble and manage applications in the PaaS cloud. The integrated, best-of-breed Oracle SOA Suite helps developers rapidly design, deploy, and manage Java services, while the complete set of tools in Oracle Business Process Management Suite allows them to create, execute, and optimize business processes.
  • Oracle WebCenter Suite provides your PaaS private cloud with a self-service portal interface, and it gives business users the ability to quickly assemble user interface components into composite applications and tailor cloud resources to their needs. The suite offers a complete, open, manageable platform that empowers both developers and business users to build, deploy, and evolve next-generation composite applications, user interface components, and portals.
  • Oracle Identity Management allows business users to centrally manage identities and security for both building and using the various applications in a PaaS cloud. Oracle offers a complete, best-in-class suite of identity management solutions for controlling the end-to-end lifecycle of user identities across all enterprise resources, both within and beyond the firewall.

These technologies provide a way for your enterprise to adopt a PaaS private cloud incrementally by progressing through various levels, or degrees of "cloudness," such as self-service enablement, elastic capacity, and so on.

"Working toward the goal of a platform-as-a-service private cloud is a great way to begin integrating your current architecture so your business can have more flexible business processes," says Andrianopoulos. "It even makes it easier to bring public cloud services into the mix with consistent management and security."

Learn more about building your own platform-as-a-service private cloud:

Understanding Row Level Security

I went through the post below from Grey Sparling Solutions Blog. This post explains the concept of row level security in a very understandable way. Go through the same.

Lot of the application groups within PeopleSoft provided their own row level security setup - HR with the security based on the department tree being a great example. The Financials group went beyond just one type of row level security "out of the box" - I forget how many choices they offered - there were several different common chart of account fields (business unit, department, account, etc.). With the application teams providing row level security in the vanilla install, many customers didn't realize that it is possible to handle row level security differently.

One thing that I always found helpful in customer meetings when this topic came up was to go through exactly how the PeopleTools component processor used search records to handle security. Once you understand that, then you can best decide if changing the row level security that the application groups provide makes sense from a cost/benefit perspective. And there definitely is a cost in the current PeopleTools - fixing row level security so that it was brain dead simple for customers to pick and choose how they wanted to implement it was one of the big ticket items planned for PeopleTools 9.

First, a quick side journey into the component processor (catch me at a conference or user group meeting sometime and I'll tell you the inside story on where the "component" name came from - it'll make you laugh). The component processor is truly the guts of PeopleTools - it is what handles the business logic, database commits, etc. for just about every page that you see in a PeopleSoft application. PeopleSoft components are parent/child hierarchies of database records that automatically get pulled together as one unit of work from the application developer's perspective.

There is one row of data at what is called Level 0. There can be up to 3 levels beyond that. Each level is required to have the same unique keys as the level above it, plus at least one additional unique key field to identify what makes the rows in that level unique.

For example, if a customer master record is at level 0 and has CUSTOMER_ID as it's unique key, you might have customer contacts at level 1 keyed by CUSTOMER_ID and CONTACT_ID. Customer contact phone numbers might be at level 2, keyed by CUSTOMER_ID, CONTACT_ID and PHONE_ID.

The data at each level comes from the key values above it. If the CUSTOMER_ID at level 0 is 1234, then the component processor would automatically use 1234 for CUSTOMER_ID for selecting data into level 1, and so on, down to level 3 (there are ways to override this, but that's how the default behaviour works).

The important thing to keep in mind here from the perspective of row level security is that populating the key fields in the level 0 record drives everything else. This is what the seach dialogs are responsible for.

When you first enter a component via the browser you get a page asking you for whatever the key fields are. In this case it would just be CUSTOMER_ID, but if the level 0 record has multiple key fields, then you'd get prompted for those as well. If you don't know the values, you click Search and get presented with a list of valid values.

But where does that list come from? Each component has what is known as a search record. The component processor uses the search record to supply the values for the key fields of the level 0 record, which then flow down to the child levels.

Any rows of data that the search record returns to the user gives the user access to that data.

So if you wanted to limit someone to only look at active customers, then you could create a view that had the same key fields as the customer master record, but had a WHERE clause like " WHERE CUSTOMER_STATUS='A' ". The view would only return active customers, which means that no one could get into that component to look at an inactive customer.

The component processor recognizes a couple of "special" fields on search records - OPRID and OPRCLASS. If the field OPRID exists on the search record, it automatically gets filled in with the current logged in user's ID. If the field OPRCLASS exists on the search record, it gets filled in with the Row Level Security Class (Permission List) that is specified on the user's security profile.

And that's essentially it for how the component processor handles things for row level security. There are a couple of PeopleCode events that fire when a search dialog is initialized (SearchInit) and when the user clicks "Search" (SearchSave), but those are not really intended for row level security. I'll write more about that in the future.

So how does the department tree security in HR work then? The HR group created a setup page that lets you pick a security class (permission list) and a tree node from the department security tree. For each one of these combos that you select, you decide whether access is granted or denied. All of this data is stored in a table. The HR team then created a view that links this table, the tree manager tables, and the employee department data together. The component processor automatically plugs in the row level security class for the user when selecting from the view, which limits what the user can see.

Financials works in a similar fashion, although the performance of the trees in the view didn't work well enough for them so they ended up with flatter security structures. The HR team actually delivered a couple of de-normalizing utilities for larger customers to deal with this issue as well.

So, how do you change that delivered security?

You could clone the delivered security views (and the tables/pages that they use to maintain the data). I helped a customer once do this where they wanted to use the position tree instead of the department tree.

You can also create your own security structures that do not mimic the delivered ones. All that matters is that you have a table or view that will return the key values that a user has access to. All that matters is that the search record has the same key fields as the level 0 record in the component that you're securing and that you either have the OPRID or OPRCLASS there to provide security.

There are no restrictions about what data the search record looks at or how that data gets maintained. For example, you might have some batch job that updates the table based on security defined in some totally different system. Or maybe someone has to request access to look at some data and security administrator will update the table that the search record looks at. I know of one customer that wanted to have their call center employees only be able to look at customer data when a call came in. So right before the server would send the screen pop for the customer data down to the agent's desktop, the security tables would be updated for that user to have access. As soon as the call was over, then access was taken away.

So the development of a new search record/view is one cost. This includes not just the technical development, but the auditing to make sure that it works properly as well.

Another cost is that the search record is attached to the component definition. So if you update a whole bunch of components to point to different search records, then you have to keep track of that at upgrade time. This is less costly than doing things like changing delivered code since you just need to add one extra step in your upgrade - update any changed components again. Not really a lot of thinking/analysis involved. But, a lot of customers like to run as close to vanilla as they can, so it is worth keeping in mind.

Of course, you don't want to be so afraid of a small cost at upgrade time if your business requirements need different data level security. I talked with a customer once that had turned off row level security in their Purchasing implementation because the delivered methods didn't work for them. Their auditors were complaining (and this was even before all of the current SarbOx push) and they wanted to know when Purchasing would support what they wanted. Changing the row level security is not so hard/costly that you'd want to run without security.


 

Strategic Structure Alignment

Found the following post interesting from Grey Sparling solutions blog.

Strategic Structure Alignment... pretty important sounding term (that probably doesn't tell you that much). It's something that probably every customer struggles with, but doesn't realize what it is.

Strategic Structure Alignment is all about making sure that the important organizational constructs are aligned across different applications and domains. In 90% of the circumstances, this is looking at how the HR responsibility structure maps to roles that people play in other systems. Throughout my years of experience with PeopleSoft applications, I've had many discussions with PeopleSoft customers about how the department chartfield in financials can be aligned with the HR employee structure (in fact, one of the remaining baby bells has a whole system dedicated to this, and we've put in enhancements to tree manager to help them handle distributed nature of this structure alignment).

There are other areas, however, where this can be applied:

  1. Row/Role level security in reporting
  2. Sarbanes Oxley compliance delegation
  3. Responsibility definition in front-line applications (such as call center and sales force automation

Basically, any place where the official reporting structure is needed to be used to drive use and functionality in an application. This is different from a knowledge network, which was discussed by Bob Stambaugh at the Northern California RUG on friday.

So, how do you align strategic structures? There are several approaches:

  1. Create one MASTER structure that gets replicated to other systems. This is the approach that the baby bell took. All information was maintained in the HR org tree, and then the tree was replicated to the other database for use in reporting. They, then made sure that the chartfield used by the tree had the appropriate values for the tree to link to (which could be a challenge). Another limitation is that you must put entries in the HR org tree that don't have any HR function in order to use them in financials.
  2. Another option is to replicate the departments in HR to financials, but not the hierarchy itself. This allows a financial organization structure to exist that does not have to exactly match the HR one (but ensures that all departments are represented financially).
  3. A third option is to synchronize the maintenance of trees between the two applications using ERI. In other words, as the user is making changes to the org tree in HR, he can drill into the appropriate tree in Financials and determine how that should be reflected there.

Because of the new requirements of Sarbanes Oxley, it is my suggestion that customers do a combination of the three approaches above. This is because the HR responsibility hierarchy will be the key to ensuring Sarbanes Oxley compliance. A good example is managing expense accounts. If you can drill down the HR responsibility hierarchy to see which people are responsibile for how much of that expense, it provides accountability and visibility into the accuracy of the financials. To accomplish this, one merely needs to provide a means for linking the HR org structure to the department chartfield in financials and drilling in nVision into a drilldown layout that uses tree nPlosion to the HR org tree.

http://blog.greysparling.com/2005/07/strategic-structure-alignment-part-1.html

Job Data Component Interface

The most used CI's for Job data creation and updation are job data Ci,job data employee CI, job data contigent worker CI and job data person of interest Ci. if a new person is hired we will go for job data employee Ci. if a contract worker is recruited we use job data contigent worker Ci. That is the distinction here. Consider in case of a rehire situation. Then we use job data component for updation. A new record cannot be created using this CI. That has to be done by the job data emp and job data cwr CI's.

One point to keep in mind here is the action and reason while updating the exisitng data.


  

Is MessageBox a Think-Time Function?

Think-time functions are PeopleCode functions that suspend PeopleSoft processing to wait for an external event (user input, an external process to complete etc). PeopleBooks strongly recommends not using think-time functions in certain PeopleCode events.

However, what category does MessageBox fall into? Well according to PeopleBooks:

If the style parameter specifies more than one button, the function behaves as a think-time function and is subject to the same restrictions as other think-time functions.

In other words, MessageBox is not a think time function when the style parameter only specifies one button! This can only be the case when the style parameter is 0 or %MsgStyle_OK which means only show the OK button. So if you use 0 or %MsgStyle_OK as the style parameter, you can use MessageBox as a normal function in any relevant PeopleCode event.

Synchronize your book marks

Synchronize your book marks where ever you go

It's a headache for me to keep the book marks synchronized between my office computer with the home and personal laptop. Yes, I thought about making an application which store the book marks online, but not in the systems hardware.

However someone else has already thought about the same and there's xmarks.com

Xmarks is a free add-on for your browser that synchronizes and backs up your favorites across multiple computers and more

Keep your life synchronized J

Validate Userid and password against LDAP directories Using PeopleCode


Following peoplecode is tested in 8.48.16 and assuming that you are using Oracle Wallet and LDAP libraries for connecting to ldap server. (Tested on HP*UX 11.11 server). It also assumes you have LDAP Port, Server name, Default Connect DN defined in PeopleTools -> Security -> Directory ->  Directory Configuration. LDAPS Port is optional but highly recommended. This can be used in following scenarios.

You are logged in PeopleSoft with generic id and you need to validate user's password against ldap directory. Or you want to see  programmatically if the user exist in LDAP with a valid password.


Create this as Class to Application Package: XX_UTILS

class LDAP
method ValidatePassword(&userid As string, &pwd As string, &directory_id As string) Returns boolean;
end-class;

method ValidatePassword
/+ &userid as String, +/
/+ &pwd as String, +/
/+ &directory_id as String +/
/+ Returns Boolean +/
Local string &defaultDN, &dn, &outDN, &server, &SSL;
Local integer &port, &nonsslport, &sslport, &EXECRSLT, &start, &num_chars, &ret;
Local Interlink &LDAP_BIND;
Local BIDocs &rootInDoc, &rootOutDoc;


SQLExec("select a.DSCNCTDN, b.DSSRVR, b.LDAPPORT, b.ldapsport from PSDSDIR a, PSDSSRVR b where a.DSDIRID = :1 and a.DSDIRID = b.DSDIRID", &directory_id, &defaultDN, &server, &nonsslport, &sslport);
If All(&sslport) Then
&SSL = "YES";
&port = &sslport;
Else
&SSL = "NO";
&port = &nonsslport;
End-If;


If All(&server, &port, &defaultDN) Then


&LDAP_BIND = GetInterlink(Interlink.LDAP_BIND);
&LDAP_BIND.UserID_Attribute_Name = "uid";
&LDAP_BIND.URL = "file://psio_dir.dll";
&LDAP_BIND.BIDocValidating = "Off";
&LDAP_BIND.SSL = &SSL;
REM &LDAP_BIND.SSL_DB = "e:\certs\cert7.db";
&start = 5;
&num_chars = Find(",", &defaultDN) - &start;
&dn = Replace(&defaultDN, &start, &num_chars, &userid);
&rootInDoc = &LDAP_BIND.GetInputDocs("");
&ret = &rootInDoc.AddValue("Server", &server);
&ret = &rootInDoc.AddValue("Port", &port);
&ret = &rootInDoc.AddValue("Distinguished_Name", &dn);
&ret = &rootInDoc.AddValue("User_Password", &pwd);
&ret = &rootInDoc.AddValue("Encrypted", "NO");


&EXECRSLT = &LDAP_BIND.Execute();
If (&EXECRSLT = 1) Then
&rootOutDoc = &LDAP_BIND.GetOutputDocs("");
&ret = &rootOutDoc.GetValue("Distinguished_Name", &outDN);
If &outDN = &dn Then
Return True;
End-If;
End-If;
End-If;


Return False;
end-method;

Sample code to call the function.

import XX_UTILS:LDAP;

Local XX_UTILS:LDAP &ldap = create XX_UTILS:LDAP();
Local boolean &return;

&userid = "userid"
&pwd = "xxxx";
&directory_id = "LDAP"; 
&return = &ldap.ValidatePassword(&userid, &pswd, &directory_id);
If &return Then
/* success */
else
/* failure */
end-if;


CTY: Ketan Kothari


How to indentify bundles that have been applied?

Question: How do i know what bundles have been applied in my PeopleSoft Application System?

Answer: All bundles update activity that are been applied to PeopleSoft system is logged into a table called PS_MAINTENANCE_LOG.you can check to this table to see what Bundles or Tax Updates have been applied. Below are the steps how to write a query in QueryTools (2 tier):

if you want a PS Query to be built, make sure you have access to this table. if you do not, you need to add this record into query security.

Bundles Query:

SELECT A.UPDATE_ID, A.DESCR, A.DTTM_IMPORTED, A.FIXOPRID, A.APPLYOPRID, A.PRODUCT_LINE, A.RELEASEDTTM, A.RELEASELABEL, A.MAINTLOGTYPE, A.DESCRLONG FROM PS_MAINTENANCE_LOG A WHERE upper(A.DESCRLONG) like '%BUNDLE%' ORDER BY 2 DESC

Tax Update Query:

SELECT A.UPDATE_ID, A.DESCR, A.DTTM_IMPORTED, A.FIXOPRID, A.APPLYOPRID, A.PRODUCT_LINE, A.RELEASEDTTM, A.RELEASELABEL, A.MAINTLOGTYPE, A.DESCRLONG FROM PS_MAINTENANCE_LOG A WHERE upper(A.DESCRLONG) like '%TAX UPDATE%' ORDER BY 2 DESC

PSUnit - Unit test framework for PeopleSoft

By david.bain

Many of you might end up building or modifying AppClasses while customizing PeopleSoft apps. AppClasses are object oriented stand alone peoplecode programs that are not tied to events, but rather have a package and class name that can be called. Applications and Tools are using these more and more so chances are if you haven't seen them you will. Want to know where . . . HCM Soa framework in 8.9/9.0 and PeopleTools message handler in 8.48 to name a couple.

To help test AppClass development, a PeopleSoft app development group built a tool called PSUnit. PSUnit is a simple testing framework that is used to write and run repeatable tests. It follows the xUnit architecture for unit testing frameworks.

Up to this point, PSUnit has only been available within PeopleSoft, but now it's available as 'open source'. Thanks to Jim Marion who took the time to clean up the pages, code, and other managed objects in the project and wrote an excellent document introducing PSUnit and describing how PSUnit can be used with Test Driven Development (TDD) projects.

The document and projects are found here:


Download project file

Introducing PSUnit

Give it a try and be sure to share your experience with other developers.

 
 

Oracle Blogs


 

  

Commencement address by Steve Jobs at Stanford University,2005

This is the text of the Commencement address by Steve Jobs, CEO of Apple Computer and of Pixar Animation Studios, delivered on June 12, 2005.

I am honored to be with you today at your commencement from one of the finest universities in the world. I never graduated from college. Truth be told, this is the closest I've ever gotten to a college graduation. Today I want to tell you three stories from my life. That's it. No big deal. Just three stories.

The first story is about connecting the dots.

I dropped out of Reed College after the first 6 months, but then stayed around as a drop-in for another 18 months or so before I really quit. So why did I drop out?

It started before I was born. My biological mother was a young, unwed college graduate student, and she decided to put me up for adoption. She felt very strongly that I should be adopted by college graduates, so everything was all set for me to be adopted at birth by a lawyer and his wife. Except that when I popped out they decided at the last minute that they really wanted a girl. So my parents, who were on a waiting list, got a call in the middle of the night asking: "We have an unexpected baby boy; do you want him?" They said: "Of course." My biological mother later found out that my mother had never graduated from college and that my father had never graduated from high school. She refused to sign the final adoption papers. She only relented a few months later when my parents promised that I would someday go to college.

And 17 years later I did go to college. But I naively chose a college that was almost as expensive as Stanford, and all of my working-class parents' savings were being spent on my college tuition. After six months, I couldn't see the value in it. I had no idea what I wanted to do with my life and no idea how college was going to help me figure it out. And here I was spending all of the money my parents had saved their entire life. So I decided to drop out and trust that it would all work out OK. It was pretty scary at the time, but looking back it was one of the best decisions I ever made. The minute I dropped out I could stop taking the required classes that didn't interest me, and begin dropping in on the ones that looked interesting.

It wasn't all romantic. I didn't have a dorm room, so I slept on the floor in friends' rooms, I returned coke bottles for the 5¢ deposits to buy food with, and I would walk the 7 miles across town every Sunday night to get one good meal a week at the Hare Krishna temple. I loved it. And much of what I stumbled into by following my curiosity and intuition turned out to be priceless later on. Let me give you one example:

Reed College at that time offered perhaps the best calligraphy instruction in the country. Throughout the campus every poster, every label on every drawer, was beautifully hand calligraphed. Because I had dropped out and didn't have to take the normal classes, I decided to take a calligraphy class to learn how to do this. I learned about serif and san serif typefaces, about varying the amount of space between different letter combinations, about what makes great typography great. It was beautiful, historical, artistically subtle in a way that science can't capture, and I found it fascinating.

None of this had even a hope of any practical application in my life. But ten years later, when we were designing the first Macintosh computer, it all came back to me. And we designed it all into the Mac. It was the first computer with beautiful typography. If I had never dropped in on that single course in college, the Mac would have never had multiple typefaces or proportionally spaced fonts. And since Windows just copied the Mac, its likely that no personal computer would have them. If I had never dropped out, I would have never dropped in on this calligraphy class, and personal computers might not have the wonderful typography that they do. Of course it was impossible to connect the dots looking forward when I was in college. But it was very, very clear looking backwards ten years later.

Again, you can't connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something — your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.

My second story is about love and loss.

I was lucky — I found what I loved to do early in life. Woz and I started Apple in my parents garage when I was 20. We worked hard, and in 10 years Apple had grown from just the two of us in a garage into a $2 billion company with over 4000 employees. We had just released our finest creation — the Macintosh — a year earlier, and I had just turned 30. And then I got fired. How can you get fired from a company you started? Well, as Apple grew we hired someone who I thought was very talented to run the company with me, and for the first year or so things went well. But then our visions of the future began to diverge and eventually we had a falling out. When we did, our Board of Directors sided with him. So at 30 I was out. And very publicly out. What had been the focus of my entire adult life was gone, and it was devastating.

I really didn't know what to do for a few months. I felt that I had let the previous generation of entrepreneurs down - that I had dropped the baton as it was being passed to me. I met with David Packard and Bob Noyce and tried to apologize for screwing up so badly. I was a very public failure, and I even thought about running away from the valley. But something slowly began to dawn on me — I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. And so I decided to start over.

I didn't see it then, but it turned out that getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again, less sure about everything. It freed me to enter one of the most creative periods of my life.

During the next five years, I started a company named NeXT, another company named Pixar, and fell in love with an amazing woman who would become my wife. Pixar went on to create the worlds first computer animated feature film, Toy Story, and is now the most successful animation studio in the world. In a remarkable turn of events, Apple bought NeXT, I returned to Apple, and the technology we developed at NeXT is at the heart of Apple's current renaissance. And Laurene and I have a wonderful family together.

I'm pretty sure none of this would have happened if I hadn't been fired from Apple. It was awful tasting medicine, but I guess the patient needed it. Sometimes life hits you in the head with a brick. Don't lose faith. I'm convinced that the only thing that kept me going was that I loved what I did. You've got to find what you love. And that is as true for your work as it is for your lovers. Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven't found it yet, keep looking. Don't settle. As with all matters of the heart, you'll know when you find it. And, like any great relationship, it just gets better and better as the years roll on. So keep looking until you find it. Don't settle.

My third story is about death.

When I was 17, I read a quote that went something like: "If you live each day as if it was your last, someday you'll most certainly be right." It made an impression on me, and since then, for the past 33 years, I have looked in the mirror every morning and asked myself: "If today were the last day of my life, would I want to do what I am about to do today?" And whenever the answer has been "No" for too many days in a row, I know I need to change something.

Remembering that I'll be dead soon is the most important tool I've ever encountered to help me make the big choices in life. Because almost everything — all external expectations, all pride, all fear of embarrassment or failure - these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.

About a year ago I was diagnosed with cancer. I had a scan at 7:30 in the morning, and it clearly showed a tumor on my pancreas. I didn't even know what a pancreas was. The doctors told me this was almost certainly a type of cancer that is incurable, and that I should expect to live no longer than three to six months. My doctor advised me to go home and get my affairs in order, which is doctor's code for prepare to die. It means to try to tell your kids everything you thought you'd have the next 10 years to tell them in just a few months. It means to make sure everything is buttoned up so that it will be as easy as possible for your family. It means to say your goodbyes.

I lived with that diagnosis all day. Later that evening I had a biopsy, where they stuck an endoscope down my throat, through my stomach and into my intestines, put a needle into my pancreas and got a few cells from the tumor. I was sedated, but my wife, who was there, told me that when they viewed the cells under a microscope the doctors started crying because it turned out to be a very rare form of pancreatic cancer that is curable with surgery. I had the surgery and I'm fine now.

This was the closest I've been to facing death, and I hope its the closest I get for a few more decades. Having lived through it, I can now say this to you with a bit more certainty than when death was a useful but purely intellectual concept:

No one wants to die. Even people who want to go to heaven don't want to die to get there. And yet death is the destination we all share. No one has ever escaped it. And that is as it should be, because Death is very likely the single best invention of Life. It is Life's change agent. It clears out the old to make way for the new. Right now the new is you, but someday not too long from now, you will gradually become the old and be cleared away. Sorry to be so dramatic, but it is quite true.

Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma — which is living with the results of other people's thinking. Don't let the noise of others' opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.

When I was young, there was an amazing publication called The Whole Earth Catalog, which was one of the bibles of my generation. It was created by a fellow named Stewart Brand not far from here in Menlo Park, and he brought it to life with his poetic touch. This was in the late 1960's, before personal computers and desktop publishing, so it was all made with typewriters, scissors, and polaroid cameras. It was sort of like Google in paperback form, 35 years before Google came along: it was idealistic, and overflowing with neat tools and great notions.

Stewart and his team put out several issues of The Whole Earth Catalog, and then when it had run its course, they put out a final issue. It was the mid-1970s, and I was your age. On the back cover of their final issue was a photograph of an early morning country road, the kind you might find yourself hitchhiking on if you were so adventurous. Beneath it were the words: "Stay Hungry. Stay Foolish." It was their farewell message as they signed off. Stay Hungry. Stay Foolish. And I have always wished that for myself. And now, as you graduate to begin anew, I wish that for you.

Stay Hungry. Stay Foolish.

Thank you all very much.