CI_JOB_DATA_HIRE component interface no longer available in 8.9
The CI for JOB_DATA_HIRE is no longer available from version 8.9 onwards. PeopleSoft's Hire process has changed and now uses 2 components therefore it is not possible to have one single CI to hire employees. The solution is to use CI_PERSONAL_DATA and CI_JOB_DATA_EMP. However, the drawback is that you need to know the EMPLID that has been generated by first CI. The solution is to use a global variable and set it when new EMPLID is assigned.
Wednesday, 18 July 2007
Thursday, 28 June 2007
Monday, 11 June 2007
Business Unit & SetIDs
From PeopleSoft ver 7.5 onwards, PeopleSoft has been providing the functionality of Business Units and SetIDs. The two elements provide greater flexibility and functionality in terms of not only managing the organisation structure but also in terms of managing and sharing setup data (i.e. departments, job codes, absence codes, locations etc). Further, the Business Units can be used for row level security i.e. to provide access to one or more business units to individual permission lists within PeopleSoft.
Business Units
Business Units represent logical units within your organization. They can be used for organisation structure and reporting purposes. By using Business Units, one can group employees by administrative organisation structure (i.e. for HR purposes) or actual business structure (i.e. Org Structure). Business Units may be, for example, companies, agencies, subsidiaries, divisions, departments, or branch offices within your organization. Alternatively, you may choose to have a single Business Unit which represents your entire organization.
TableSets and SetIDs
Once Business Units have been defined, you can define TableSets, or groups of tables, for your setup/control tables, so that you can share the same code values across more than one Business Unit within your organisation. Additionally, the TableSet feature also allows you to restrict access to specific data to only those users who need it, while storing all of your data on the same tables. This flexibility enables organisation to centralise common data / information whereas the other data/information can be decentralised i.e. Departments, Job Codes, Absence Types etc. A Business Unit is then associated with employee's Job record in the organisation and using Business Unit, you can specify how the defaults for currencies and country codes will work.
Where a Business Unit organizes your company or your organization, SetIDs help you organize your data within the system. The HRMS system uses tables (Control Tables or Prompt Tables) that use a high-level key that enables you to identify and retrieve data from the system. A secondary high-level key, referred to as a SetID, has also been added on various tables. SetIDs are simply the labels used to identify a TableSet. Business Unit and SetID functionality in PeopleSoft HRMS also provides you with a higher business level for reporting purposes and other business data roll-up.
Business Units
Business Units represent logical units within your organization. They can be used for organisation structure and reporting purposes. By using Business Units, one can group employees by administrative organisation structure (i.e. for HR purposes) or actual business structure (i.e. Org Structure). Business Units may be, for example, companies, agencies, subsidiaries, divisions, departments, or branch offices within your organization. Alternatively, you may choose to have a single Business Unit which represents your entire organization.
TableSets and SetIDs
Once Business Units have been defined, you can define TableSets, or groups of tables, for your setup/control tables, so that you can share the same code values across more than one Business Unit within your organisation. Additionally, the TableSet feature also allows you to restrict access to specific data to only those users who need it, while storing all of your data on the same tables. This flexibility enables organisation to centralise common data / information whereas the other data/information can be decentralised i.e. Departments, Job Codes, Absence Types etc. A Business Unit is then associated with employee's Job record in the organisation and using Business Unit, you can specify how the defaults for currencies and country codes will work.
Where a Business Unit organizes your company or your organization, SetIDs help you organize your data within the system. The HRMS system uses tables (Control Tables or Prompt Tables) that use a high-level key that enables you to identify and retrieve data from the system. A secondary high-level key, referred to as a SetID, has also been added on various tables. SetIDs are simply the labels used to identify a TableSet. Business Unit and SetID functionality in PeopleSoft HRMS also provides you with a higher business level for reporting purposes and other business data roll-up.
Tuesday, 29 May 2007
Copy Missing Departments after Tree Copy
Since Copying a Tree via App Designer doesnt copy the department records in DEPT_TBL, the tree and department table may become out of sync. Here is a little SQl to copy Department records in DEPT_TBL once you have copied the Tree. The SQL is for SQL Server platform and relies on database links.
INSERT INTO PS_DEPT_TBL
SELECT B.* FROM PSTREENODE A, HCMPRD88.dbo.PS_DEPT_TBL B
WHERE A.TREE_NAME = 'DEPT_SECURITY'
AND A.EFFDT = '2006-01-01'
AND NOT EXISTS (SELECT 'X' FROM PS_DEPT_TBL
WHERE A.TREE_NODE = DEPTID)
AND A.TREE_NODE = B.DEPTID
In version 8.8 and abover, PeopleSoft provides a web based page to export and import Tree. This can be accessed via -Company Hierarchy, Administer Tree, Copy/Delete Tree.
INSERT INTO PS_DEPT_TBL
SELECT B.* FROM PSTREENODE A, HCMPRD88.dbo.PS_DEPT_TBL B
WHERE A.TREE_NAME = 'DEPT_SECURITY'
AND A.EFFDT = '2006-01-01'
AND NOT EXISTS (SELECT 'X' FROM PS_DEPT_TBL
WHERE A.TREE_NODE = DEPTID)
AND A.TREE_NODE = B.DEPTID
In version 8.8 and abover, PeopleSoft provides a web based page to export and import Tree. This can be accessed via -Company Hierarchy, Administer Tree, Copy/Delete Tree.
Monday, 21 May 2007
Role, Permission List that contain a Page
select A.CLASSID , B.CLASSDEFNDESC, C.ROLENAME, D.DESCR
FROM PSAUTHITEM A, PSCLASSDEFN B, PSROLECLASS C, PSROLEDEFN D
WHERE A.PNLITEMNAME = 'COMPETENCY_TABLE'
AND A.CLASSID = B.CLASSID
AND A.CLASSID = C.CLASSID
AND C.ROLENAME = D.ROLENAME
FROM PSAUTHITEM A, PSCLASSDEFN B, PSROLECLASS C, PSROLEDEFN D
WHERE A.PNLITEMNAME = 'COMPETENCY_TABLE'
AND A.CLASSID = B.CLASSID
AND A.CLASSID = C.CLASSID
AND C.ROLENAME = D.ROLENAME
Subscribe to:
Posts (Atom)
