Wednesday, October 2, 2013

How date format works on Activity based email notification

Below are the sequence of steps the activity checks for date format.

  1. Initially this looks for user defined date format in Regional Settings.
  2. If above setting is not defined then this looks for the date format set for the browser language option settings.
  3. if above 1 and 2 settings are blanks, then this takes the date format from system level defined settings.

Details of each step with screenshots.

1. User can define date format in My personalizations.

ate1

2. Local default settings for browser language options.

date2

“M stands for MM/DD/YYYY” and “D stands for DD/MM/YYYY”.

Browser language option looks like below.

date5

3. System level default settings.

date4

Tuesday, May 21, 2013

Analytic Engine and Analytic Grid with simple Example

This example is to understand how to create and use Analytic Grid and Analytic Engine which is available in PeopleTools.

This is a simple example to create Read Only Analytic Grid without any PeopleCode used.

This can be more complex if Analytic Grid is used as Read/Write. (I will not cover Read/Write Analytic Grid in this example).

Example: To Create Analytic Grid for Location based Department based Head Count from Job record.

Preview:

 image

Below Steps are used to create Analytic Grid for above example:

Note: Analytic Grid can be based on Physical Record or View. However if view is used then the Analytic Grid will be read-only. For read-write analytic grid physical record is required with the version record.

As this example is to demonstrate only read-only I am using view for this example.

Step 1: Create a view over Job record or Job effective date view with LOCATION, DEPTID, PM_COUNT fields. This is used for Analytic Grid Data Cube Collection

a) Create a view and insert the fields to the record LOCATION, DEPTID, PM_COUNT. PM_COUNT is a number field and LOCATION and DEPTID as Primary Key.

b) Save the view as “PM_HEADCOUNT_VW”

c) Provide the below SQL in the view.

SELECT LOCATION
, DEPTID
, COUNT(*) AS PM_COUNT
  FROM PS_PM_JOB_VW
  GROUP BY LOCATION
  ,DEPTID

Step 2: Create a work record which is used for Analytic Grid Presentation Cube Collection.

a) Create a work record with LOCATION, DEPTID, PM_COUNT fields.

b) Save the work record as “PM_HDCOUNT_WRK”

Step 3: Creating Analytic Model.

a) Create New Analytic Model from Application designer.

b) Right click on the “Dimension” and create two dimensions as LOCATION and DEPTID as shown in the image.

image

c) Save the Analytic Model as “PM_HEADCOUNT_AM”

d) Right Click on the Cubes and Create “HEADCOUNT” cube and attach “LOCATION” and “DEPTID” dimensions to the cube as shown below.

image

e) Right Click on the Cube collection and create “DATACUBECOLLECTION” cube collection and associate “HEADCOUNT” cube to the Cube Collection and assign the created view “PM_HEADCOUNT_VW” in “Main Record” section of General Tab as shown below.

 image

f) Map the appropriate fields in “Field Map” Tab as shown.

image

g) Right Click on the Cube collection and create “PRESENTATIONCUBECOLLECTION” cube collection as above and associate “HEADCOUNT” cube to the Cube Collection and assign the created work record “PM_HDCOUNT_WRK” in “Main Record” section of General Tab as done for “DATACUBECOLLECTION”. Map the appropriate fields in the “Field Map” Tab.

image

h) Create “Explicit Dimension Set” to filter value based on Location or Department. To Create “Explicit Dimension Set” Click on “Explicit Dimension Set” shown in above example and right click to add “Add Dimension Set”. Add the dimension set as shown in the below Image.

image

i) Save the Analytic Model.

Step 4: Creating Analytic Type.

a) Create new Analytic Type from application designer and associate the Analytic Model (PM_HEADCOUNT_AM) to this Analytic Type. To add Analytic Model click on “Model Tab” of Analytic Type and from Menu bar under Inset menu select “Analytic Model..”. Select the PM_HEADCOUNT_AM Analytic model and this will add into Analytic Type.

image

b) Save the Analytic Type as “PM_HEADCOUNT_AT”.

Step 5: Creating Analytic Instance.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Inst. Create/Del/Copy in the PIA.

b) Select the Analytic Type (PM_HEADCOUNT_AT) and Provide the Analytic Instance name (PM_HEADCOUNT_IN). Click on “Create Analytic Instance” button.

image

c) This will create the Analytic Instance “PM_HEADCOUNT_IN”.

Step 6: Load Analytic Instance.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Instance Load/Unload in the PIA.

b) Search for “PM_HEADCOUNT_IN” (i.e. Appropriate instance name according to you)

image

c) Click on “Load Analytic Instance” button from the below Screen to load the Analytic Instance.

image

Step 7: Verify Analytic Model using Analytic Model Viewer.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Model Viewer.

b) Search the Analytic Instance “PM_HEADCOUNT_IN” and click on the instance link.

c) Select the “PRESENTATIONCUBECOLLECTION” to view the Analytic Model functioning.

image

image

Step 8: Create a Page with Analytic Grid to associate the Analytic Model to Analytic Grid.

a) Create a Page and Place an Analytic Grid control to the Page.

b) Add the work record(PM_HDCOUNT_WRK) fields in the Analytic Grid which is as main record in “PRESENTATIONCUBECOLLETION” cube collection.

image 

c) Set the properties of the Analytic grid as follows.

image

d) Analytics Instance in the Grid Properties shown above is the page field placed in the page and this field has the value of Analytic Instance which is created through online (PM_HEADCOUNT_IN). This value(Analytic Instance) is assigned in prebuild event of component. (Create a separate work record with a field to assign analytic instance on this. Analytic instance can be assigned as <Recod>.<Field>.Value = “<ANALYTIC_INSTANCE>” for this example PM_HEADCOUNT_WRK1.DESCR.Value = “PM_HEADCOUNT_IN”).

e) Save Page and Component. (INSTALLATION record can be used as search record to bypass search page).

f) Register the component and View the page online and see the Analytic Grid Functioning.

image 

Note: Make sure “Analytic Server” is UP and running in “Application Server”.

Thursday, April 11, 2013

PS Mobile/Tablet Solutions

Delivered:
  • Mobile Company Directory - Doc ID 1494986.1 and 1494952.1
  • Mobile Approvals - Doc ID 1505021.1
  • Mobile Expense - Doc ID 1505021.1
  • Mobile eProcurement
Planned Solutions(In Future Releases):
  • Time and Labor
  • Absence Management
  • Cash Position Management
  • HR Self-Service
  • Dash Boards
                    Some more details documented on document id: 1504427.1
                    For video features: Document ID: 1362821.1

                    Saturday, March 30, 2013

                    One Stop Shop for all useful Queries

                    I have created an Excel Tool to collect the Useful Queries in one place, i.e. One Stop Shop for all useful Queries.
                    Use of this Tool:
                    1. This can be used for One Stop Shop for all the queries used in Development And Support.
                    2. This can be used for One Stop Shop for all your personal Queries.. (As local Copy)
                    Download Link: Excel Tool To store all Useful Queries



                    Tuesday, March 5, 2013

                    PeopleTools 8.53 Improvements

                    Some important improvements got introduced in how customers deploy, scale, and update peoplesoft applications with features like virtualization and the PeopleSoft Update Manager (PUM).

                    Here are some of the major improvements in PeopleTools 8.53 release:

                    • Oracle’s Secure Enterprise Search – Provides secure, free-text search within PeopleSoft applications across multiple objects and multiple applications for a more streamlined search-driven navigation approach.
                    • Related Actions – Enables end users to take relevant actions on objects within the context of transactions rather than using lengthy traditional menu paths.
                    • Activity Guides – Provides for the deployment of guided business processes, which facilitate a variety of activities from self-service to administration.
                    • Pivot Grids – Offers self-service, real-time, multi-dimensional analytics embedded into PeopleSoft applications providing end users with the actionable information needed to make decisions.
                    • WorkCenters – Consolidates user tasks, exceptions, alerts, links, reports, and queries into a single, secure, role based “command center” that can be personalized and configured by end users for increased productivity.
                    • Cascading Style Sheets (CSS) – Improves use and support of CSS and enables customers to easily configure their PeopleSoft system to reflect organizational branding (e.g. color, graphics, etc.).
                    • Oracle Private Cloud Deployments of PeopleSoft – Enables multiple PeopleSoft application instances to be consolidated on Oracle Exalogic, providing high capacity and performance, dynamic scaling and provisioning using Oracle Virtualization.  This also dramatically improves system management, patching, and maintenance.  All of this reduces total cost of ownership.
                    • Secure by Default - As part of Oracle Secure by Default initiative, PeopleTools 8.53 will request passwords for delivered accounts necessary for system initialization and disabling other sample accounts. We will also be delivering a salted SHA-1 hash for PeopleSoft passwords. The salted SHA-1 hash enhancement will not affect upgrades.

                    Tuesday, January 22, 2013

                    Minimum RDMS Privileges of the PSADMIN Role

                     

                    |--------------------+------------------------------------+------------| 
                    | | | |
                    | Privilege | Comments | Removable? |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | ALTER SESSION | This is done during some SQR | No |
                    | | processes and is also necessary to | |
                    | | enable SQL tracing during | |
                    | | performance tuning | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | ALTER TABLESPACE | PeopleSoft does not alter the | Yes |
                    | | tablespace itself, this is a job | |
                    | | for the DBA instead. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | ALTER ROLLBACK | The rollback segments should be | Yes |
                    | SEGMENT | completely maintained by the DBA. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE CLUSTER | PeopleTools cannot do this | Yes |
                    | | directly and is therefore not a | |
                    | | function of PeopleSoft, but could | |
                    | | be an option for performance | |
                    | | tuning that the DBA may wish to | |
                    | | take | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE DATABASE | Private database links are used | Yes |
                    | LINK | during the upgrade compare | |
                    | | process. Although, perhaps only | |
                    | | the DBA should be creating | |
                    | | database links. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE PUBLIC | Public database links are not used | Yes |
                    | DATABASE LINK | by PeopleSoft | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE PUBLIC | Public synonyms are created during | No |
                    | SYNONYM | the upgrade compare process | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE SEQUENCE | Sequences are not used by | Yes |
                    | | PeopleSoft | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE SNAPSHOT | PeopleSoft does not use snapshots | Yes |
                    | | by default, but they can be used | |
                    | | to maintain generated tables. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE SESSION | This allows connection to the | No |
                    | | database and is essential | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE SYNONYM | Private synonyms are created for | No |
                    | | PSOPRDEFN and PSLOCK for each user | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE TABLE | Data Designer created tables | No |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE VIEW | Data Designer creates views | No |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE PROCEDURE | Not used directly by PeopleSoft. | Yes |
                    | | Useful in conjunction with | |
                    | | triggers. Before Oracle 7.3 would | |
                    | | be needed in conjunction with | |
                    | | triggers as triggers are not | |
                    | | compiled, whereas packaged | |
                    | | procedures are. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE TRIGGER | PeopleSoft does not use triggers | Yes |
                    | | by default. However this is an | |
                    | | option for additional auditing. | |
                    | | In which case CREATE PROCEDURE | |
                    | | would be an advantage too. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE TABLESPACE | PeopleSoft does not alter the | Yes |
                    | | tablespace itself, this is a job | |
                    | | for the DBA instead. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE USER | A new database user is created | No |
                    | | when a new PeopleSoft user is | |
                    | | created | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | CREATE ROLLBACK | The rollback segments should be | Yes |
                    | SEGMENT | completely maintained by the DBA. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | DROP PUBLIC | Public database links are not used | Yes |
                    | DATABASE LINK | by PeopleSoft | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | DROP PUBLIC | Public synonyms may be dropped | No |
                    | SYNONYM | during the upgrade compare process | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | DROP ROLLBACK | The rollback segments should be | Yes |
                    | SEGMENT | completely maintained by the DBA. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | DROP TABLESPACE | PeopleSoft does not alter the | Yes |
                    | | tablespace itself, this is a job | |
                    | | for the DBA instead. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | DROP USER | A database user is dropped when a | No |
                    | | new PeopleSoft user is removed | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | MANAGE TABLESPACE | This allows tablespaces to be | Yes |
                    | | taken on and off line during a | |
                    | | backup. This is a job for the DBA | |
                    | | instead | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | RESOURCE | This is equivalent to CREATE | Yes |
                    | | CLUSTER, CREATE PROCEDURE, | |
                    | | CREATE_SEQUENCE, CREATE TABLE, and | |
                    | | CREATE TRIGGER that are all dealt | |
                    | | with explicitly elsewhere. It is | |
                    | | used for compatibility with | |
                    | | previous versions of Oracle7. | |
                    | | Thus is privilege is not required | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | EXP_FULL_DATABASE | Full exports could be performed by | Yes |
                    | | the DBA rather than the PeopleSoft | |
                    | | system administrator. This also | |
                    | | implies SELECT ANY TABLE. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | IMP_FULL_DATABASE | Full imports could be performed by | Yes |
                    | | the DBA rather than the PeopleSoft | |
                    | | system administrator This also | |
                    | | implies BECOME USER. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | GRANT ANY ROLE | This privilege is required in | Yes |
                    | | order to grant the PSUSER role to | |
                    | | the new database user when | |
                    | | creating a PeopleSoft user in | |
                    | | Operator Security. However, if | |
                    | | the PSUSER role is granted to | |
                    | | SYSADM with the ADMIN OPTION then | |
                    | | SYSADM can still grant PSUSER and | |
                    | | GRANT ANY ROLE is no longer | |
                    | | required. | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | ALTER USER | This allows the user, amongst | No |
                    | | other things, to change passwords. | |
                    | | It is therefore required | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    | | | |
                    | BECOME USER | This is required by and implicit | Yes |
                    | | in IMP_FULL_USER, but is not | |
                    | | otherwise required by PeopleTools | |
                    | | | |
                    |--------------------+------------------------------------+------------|
                    Source: Oracle Doc ID: 1140413.1