PeopleSoft Learning

PeopleSoft ERP delivered Business Process might not be application for all customers. Customer prefer to change the PeopleSoft rather than change their business process to suite their requirements.
Customizing PeopleSoft all time is not good idea, can we avoid it ? No, we cannot avoid customization to PeopleSoft Application as it might not suite customer requirements.
Lets see what are the options provided by PeopleSoft to avoid Customization to delivered objects so that it will be easy to handle during the customization and retro-fit efforts are reduced.
1) Most common customization is to add additional fields on the delivered components to Capture additional information.
    a) Related Content Framework - it can be used to display additional custom page in the delivered component where additional parameters can be captured. It is very powerful solution where you can display the page from PeopleSoft, Query Results, External Application, Web applications.
      Related Action Framework - Will help to related different related transaction.
   b) Common Attribute Framework - It is an feature in the Campus Solution - where many of the delivered component related to Student/Prospect Personal information loaded from PDL process and processed from admission application. Using the simple configuration we can store additional values in different format like Scroll and Attributes. This can be applicable for other pages with minimal configuration. This feature should be available for HCM and FSCM as well.
2) Creating New Custom Approval Workflow Process.
   Workflow in an Important feature required of the Business Process, most of the configuration for AWE can be done online, but what if the customer need New Approval Process ?
PeopleSoft Forms and Approval Builder enables business analysts to create electronic, routable forms without having to use PeopleSoft Application Designer. A typical form can be designed and in use within 30 minutes and requires no writing of code. The intuitive wizard guides you step by step through establishing a form. Options include adding instructions to the form, similar to what you would find on the back of a paper form; adding attachments to the form for users to read, submit, or both; and being able to create your own fields on the form. On Final Approval - Component Update from CI is possible using the configuration.
This is available from PeopleSoft 9.1 on-wards and hence available for Peopleoft HCM, FSCM, CRM only and yet to available for PeopleSoft Campus Solution.
3) Creating an Webservice/Interface for the External System to get the real-time data from PeopleSoft.
   a) CI Based Web service - Which doesn't need any code development where component can be operated easily and no coding and customization is required.
    b) If the data is required to be fetched from other than the component - CI will not be applicable.
QAS - Query as Web service - Creating Simple Query can pull the data from multiple records and apply data security and other business logic. It is easy to create this webservice and third party system can make use of it. It can be simple interface for the Down stream system.
4) Reading Inbound interface file or loading the data from file - It is one of the common requirement.
    File Parser  - is a Campus Solution feature it not available for HCM, FSCM and CRM Application. it is very useful to load any data from File, without any coding required.
5)  Sending Emails/Work list/Notifications for different users on Events in the PeopleSoft Application -
  Following method doesn't avoid customization but reduce the amount customization and retro-fit effort. It will be standard method to send Worklist, Emails - Which can be easily tracked. It should be used as standard method and Best practice as it has a lot features that can used with less customization.
Events and Notifications Framework
The PeopleSoft Events and Notifications framework provides three features that can be configured and used to monitor business processes and create messages when unusual situations or errors occur within a PeopleSoft process or table. These messages can be routed to different users (PeopleSoft or non-PeopleSoft) to prompt the user to resolve the issue. Links can take the user directly to the page for correction or resolution.
The three features are: • Events • Notifications • Alerts

Following is the simple code Raise the event, Event handler can handle the rest.
import EOEN_MVC:EOEN_MODEL:EOENInterface;
Local EOEN_MVC:EOEN_MODEL:EOENInterface &myEvent;
Local Record &recContext;
&myEvent = create EOEN_MVC:EOEN_MODEL:EOENInterface("", 0);
&recContext = &rsContextRec(1).GetRecord(Record.CONTEXT_REC);

&myEvent.AddContextRecord(&recContext); &myEvent.RaiseEvent("EventName");