Hi,
Its been a while since I updated this blog, but I was busy with other things. Well, here is the next post in which we will see how to secure chartfields.
The first question is - what is the need to secure them?
The answer is that different users in the organization will have different needs and different levels of data access. To conform to this scenario, PeopleSoft allows administrators to configure data access to different users based on their roles and needs.
To implement this security feature efficiently, PeopleSoft allows security to be set by roles, user or permission list. This feature is enabled only for those pages that have amount fields and other sensitive information. Sensitive data could be categorized as assets, inventory and other expense related items.
Chartfield Security feature allows :
To set up Chartfield security, you have to follow the steps below :
The above is all that is needed to implement chartfield security. Of course, each individual product will have its own components to be secured. This is something that is being left to the reader to explore.
The next posts will move out of PS Application Fundamentals and will focus on implementation steps for PS FSCM modules.
Its been a while since I updated this blog, but I was busy with other things. Well, here is the next post in which we will see how to secure chartfields.
The first question is - what is the need to secure them?
The answer is that different users in the organization will have different needs and different levels of data access. To conform to this scenario, PeopleSoft allows administrators to configure data access to different users based on their roles and needs.
To implement this security feature efficiently, PeopleSoft allows security to be set by roles, user or permission list. This feature is enabled only for those pages that have amount fields and other sensitive information. Sensitive data could be categorized as assets, inventory and other expense related items.
Chartfield Security feature allows :
- Enabling & disabling access based on product, component, user, role or permission list.
- Restricting access to transactions containing unauthorized Chartfield values, distribution code values in relevant components, financial data containing unauthorized Chartfield values in Inquiry components, unauthorized Chartfield values during data entry.
- Specify components as exceptions for users, role or permission list.
- From Component search lists
- From Inquiry Page lists
- From Inquiry results
- From Drills to transaction components
- From Prompt edit table values
- From Distribution codes
To set up Chartfield security, you have to follow the steps below :
- Define security options and products
- Identify security requirements
- Define and assign security rules
- (Optional step) Copy security rules for users, roles or permission lists
- Identified chartfields that meet the security requirements
- Security levels that are needed
The above is all that is needed to implement chartfield security. Of course, each individual product will have its own components to be secured. This is something that is being left to the reader to explore.
The next posts will move out of PS Application Fundamentals and will focus on implementation steps for PS FSCM modules.
