Thursday, January 14, 2016

Change Control in PeopleSoft to track changes and avoid overwriting

     Change Control in PeopleSoft

  • Change control in peoplesoft is mechanism provided to track the changes and help to avoid overwrite the changes done by a user on same object at the same time.
  • This option can be enabled from application designer from Tools --> Change Control --> Administrator as shown in the below image.


  •  This option can be enabled by administrator only and when there is no user login to the application designer.
  • Also, to track the changes done to the objects this option Use change control history should be enabled and ticked.

*****************************Thanks*********************************

Create Popup menu in PeopleSoft

Creating a popup menu in PeopleSoft is quite simple.

You can follow the steps given below to implement a popup menu on your page.

1) In application designer go to File > New and select Menu

2) On the second page a small window opens that shows standard and Popup option Select Popup.

3) Once the popup menu is selected click ok and it will take to a new menu page where you have to double click on the menu to add an item to the popup menu. give some name and label to menu.

4) Select the type of action. If it is a simple transfer to a new page, select Transfer. If you are planning to execute your code, then select PeopleCode. If you have selected Transfer option, then provide the details of the page, menu, component and action.

5) If you have selected PeopleCode option, then right click on the menu item and select View PeopleCode. It will open the Menu Item selected PeopleCode event. Write the logic or code you plan to implement over here.

6) You have successfully created a popup menu. Now you need to add it to a page field. For that open the Page Field Properties of the field you plan to implement the popup menu. Go to the Use tab and provide the name of the popup menu you have just created in Popup Menu edit box.

Once the popup menu name is added to the page filed. here for example I have name field on the page so the popup menu would be seen as shown below:



 




Once we click the popup menu it would open the popup menu added page either in same re-use or new window as given during the time of creation of it.

**********************************Thanks***********************************

Monday, January 11, 2016

PeopleSoft 8.53 Installation Steps


Peoplesoft Installation 8.53 Steps:

First we need to check the certification details for the peoplesoft peopletools, application, jdk, tuxedo and weblogic version with the hardware and operating system version. This details can be obtained from support.oracle.com

We are going to Install with the certification for peoplesoft 8.53 on Windows 7 and database as Oracle 11g Release 2.
  1. Install the softwares one by one in the order mentioned for peoplesoft 8.53:
  2. Install the Oracle Database 11g R2 (64-bit)
  3. Install JDK for Windows 7 64-bit
  4. Install Tuxedo 11g V2010 Windows 64-bit
  5. Install WebLogic Server 10.3.6.0 in 64-bit mode
  6. Install PeopleTools 8.53 (Disk1, Disk2 and Disk3)
  7. Install PeopleSoft HCM 9.2 (Disk1)

Creating PeopleSoft Oracle Database:
  1. Create the Oracle Database using Database Configuration Assistant (DBCA). Once created the Oracle database it is blank we need to run six SQL Scripts to create peoplesoft objects like records, temporary records, users, etc
  2. Run UTLSPACE.SQL – This will create Catalog Views and Utility tablespaces like PSDEFAULT and PSTEMP
  3. Run HCDDL.SQL – This will create Application related tablespaces. Make sure you have disk space on the oradata or where the data files will be created.
  4. Run DBOWNER.SQL – This will create PS.PSDBOWNER table where it holds two columns Database Name, OwnerId. This table exists in Oracle only not when you create a database in SQL Server.
  5. Run PSROLES.SQL – This will create PeopleSoft related database roles.
  6. Run PSADMIN.SQL – This will create PeopleSoft database Owner ID (By default we give SYSADM)
  7. Run CONNECT.SQL – This will create Connect ID (people) which is used in the initial connection to connect to the peoplesoft database.
  8. Configure the PeopleSoft Configuration Manager. Set the Database Name, Type, Connect ID, Password, etc.
  9. Now we can run the Database Setup using Data Mover to run the Import database Script which uses the (.db files) to create the peoplesoft database which can be a Demo, System or Peopletools database based on the selection.
  10. Now, the Import Script will take some time to create peopesoft records, temporary records, views, etc.
Once the peoplesoft database is created with the import script, we need to check the PSSTATUS table for the version specified in the toolsversion column. If the version is the same as 8.53 it means we had the updated peopletools objects and system data. So, we can proceed to run the final scripts and complete the process.

Run VERSION AE program - It udates the PSVERSION table for the version.
Run DDDAUDIT.SQR - This will show the inconsistencies if any in the newly created database.
Run SYSAUDIT.SQR - This will show the orpahed objects if any there in the database.
Run SETSPACE.SQR – This SQR will synchronize the tablespace details with the system catalog.
Run ALTERAUDIT – This will synchronize the peopletools tables with the underlying SQL data tables.

Peoplesoft Create Domains
  • We had few videos on how to create Application Server and Web Server Domains at this blog. Please refer to that.
  • Boot the Domains Web Server, Application Server, Process Scheduler (After configure Report Nodes).
  • Login to PIA (URL - http://servername:http_port/sitename/signon.html

 *******************************Thanks*****************************

For PeopleSoft DBA Trainings / Technical Trainings please contact at

info@orainstall.com

Also we do PeopleSoft Virtual Installation /  on your system for learning purpose

PeopleSoft Security Tables


Below are few tables that are involved in PeopleSoft Security:-

  • PSROLECLASS: It is Role Classes table. A many to many relationship table between Roles and Permission Lists.
  • PSROLEDEFN: This table stores information about PeopleSoft Role definitions. Users get permissions to PeopleSoft objects through Roles, which are assigned Permission Lists.
  • PSROLEUSER: This table stores information about the Users in PeopleSoft and the roles assigned to them.
  • PSCLASSDEFN: Permissions List definitions table. Permission list name can be found under Field Name CLASSID.
  • PSOPRDEFN: Users/Operator definition table. This table stores information about PeopleSoft users. This is the core table for User Profile Manager.

*******************************Thanks For the Visit **************************

FFreshers / Students:-

     For making career in PeopleSoft and learn PeopleSoft Technical / DBA / Functional Please visit www.orainstall.com

PeopleSoft Security Basics


Why PeopleSoft Security?


Peoplesoft is a client server application suite based on client server architecture. It is similar to other ERP systems, which connects to RDBMS as backend, and that can be Oracle , IBM DB2, Informix, Sybase, SQL Server etc, based on client environment. 

Since Peoplesoft HRMS is a productive product suite, Security is mandatory , as the data mainly deals with personal information such as SSN, credit card etc, So there should be sufficient provision of security towards the data accesses.

All users are not exposed and given the same access towards the application and only authorized user have the access to application servers. All this things are handled by security principles defined with the help of peoplesoft security.

The PeopleSoft Internet Architecture falls into the category of PeopleSoft online security, also known as runtime security, which means that only authorized users can connect to the web and application servers, and only authorized application servers can connect to a backend database.

PeopleSoft Security           
T   
     PeopleSoft security approach is tailored specially for the internet. PeopleTool Security enables provision of security to all of the users of PeopleSoft system.
     Using the Definition Security People Tool we can restrict access to the objects developers created in PeopleSoft Application Designer.
 
Below are some terms Used while implementing Peoplesoft Security

USER ID          - Enables access to system.
                     -  Authenticates, Authorizes. 
ROLE              -   A named set of work that a user can do.
                     -   Works in conjunction with Workflow.
                     -   Comprised of “1 or more” Permission Lists.
PERMISSION
LIST               - Defines the pages to which the employee is                                                                  authorized to gain access.

Different types of Security
Sign on and Time-out Security:-

User is asked to enter User ID and a password on the PeopleSoft Sign on page also called as PIA page, when signing into PeopleSoft. For a valid userid ID and password, PeopleSoft connects the user to the application and the system retrieves the appropriate user profile. When a user signs on, they are connected as long as their sign on time allows and as long as their browser doesn’t sit idle for longer than their time-out interval is met.

Page and Dialog Security:-
            
Page and Dialog Security is used for granting access to PeopleSoft menus, Users can be controlled from accessing the data with the help of Peopletool Security.    

Batch Environment Security:-

For running a batch Processes from PeopleSoft Process Scheduler, appropriate Process Profile to the User Profile should be assigned along with proper process groups.
Each batch program has a run control that we define before we can run the batch program.

Definition Security:-

For restricting the access of application developers, a separate People tool called ‘Definition Security’ is used , which can be used to govern access to the Record definitions, Field definitions, but Page definitions as well.

Application Data Security:-

Definition Security is a type of data security- which is used to control access to object definitions in the People tool tables. We can set data permissions at the following levels:

Ø  Query/Table-Level Security:-  Query/Table Level Security helps us to build SQL queries to 
retrieve information from application tables.
Ø  Row-Level Security:-  Row Security Permission list is used to define data security to users.
Ø  Field Security:-  We can restrict the access to particular fields or columns within our 
application tables by using People code.

************************************Thanks for reading *************************

     Freshers / Students:-

     For making career in PeopleSoft and learn PeopleSoft Technical / DBA / Functional Please visit www.orainstall.com