How can I implement row level security in Peoplesoft CRM v8.8?

A: You can design special types of SQL views -security views- to control access to individual rows of data stored within your application database tables. Your Pe opleSoft applications are delivered with built-in, row-level security functions, tailored to that specific application. For example, in PeopleSoft HRMS, we provide security tables that enable you to r estrict operator access to employee rows according to organizational roles, or t o permit an operator to view and update rows for employees in their department o nly. Then to get the security down to the operator ID level instead of the operator c lass level, there are steps defined in Designing Your PeopleSoft Human Resources System manual under Using Operator IDs for Employee Data Security. Changing operator class to operator ID Steps to implement Organizational Security by OPRID: 1) Delete all entries for each OPERClass/OPERID in Security Tables. 2) Run SECVWTRE.WT to load the SQL text for the security views(only needs to be performed if organizational security has been turned off). 3) Run SECBYOPR.WT to change the view text of Oprdefn to select based on Oprtyp e of 0 (instead of 1 for operator class security. 4) Add the field OPRID in place of the OPRCLASS field in the search views and ma ke it a key item. 5) Recreate the search views and the Oprdefn view. 6) After the departments have been loaded, create a tree with effective date the same as the effective date for the departments equating the node with the depar tment ID. 7) Run PER505 to update the effective date of PS_R_PER505. 8) Update the security tables to show which departments each operator or operato r class has authorization to read/write. 9) Run PER505 if any changes are made to the tree structure. This will update th e security tables established in 6 to reflect the changes to the hierarchy. To switch from Operator Class to Operator ID security: 1) If you have department security in place for an OprID or OprClass delete thes e entries now, they will not be available after updating the Oprdefn view and ma y give inaccurate results if left in place. 2) Run SECBYOPR.WT to change the view text of Oprdefn to select based on an Oprt ype of 0. (To switch back to Operator Class security run SECBYCLS.WT to switch t he view text of Oprdefn to select based on an Oprtype of 1.) 3) Recreate the Oprdefn view. 4) Change each search view and replace the OPRCLASS field with OPRID field and m ake OPRID a key field. 5) Set up the tree and department security as in the steps 5 through 8 under Ope rator ID security setup. Change Standard Search Record into OPRDEFN_DEPT. The view text in OPRDEFN_DEPT should look like this: SELECT A.OPRID ,A.EMPLID FROM PSOPRDEFN A

WHERE A.OPRTYPE=0 You must rebuild this view. _________________________ Q: Will u tell me what is meant by Dynamic Prompt Table? How can we create? How to use a Dynamic prompt table? what we need to do for it? what should be the len gth of the field? A: Prompt Table: A list of values from which a user can look up and select a value and fill the field on the page. Prompt Table will be assigned in Record Field Properties Prompt Table can of 3 types Prompt Table with Edit: If u set this property and give the table as prompt table in the following text box field in record field properties.Then it implies that user should enter the value which was already there in the Prompt table. Prompt Table with No Edit: If you set this property, it implies that user can either select one of the val ues from the prompt table or he can give his own value which can be store in the table (Not Prompt table :)) So here Prompt table serves as just list of referen ce values which peoplesoft allows user to select from the list or enter his own value. Traslate edit (Yes/No) with edit: If you set this Property then, you should select Yes or No values. Dynamic Prompt Table: What we discussed untill now, can be called as Standard Prompt table or Prompt Table or Static Prompt Table. Let us assume, we have a situation where we want t o change the prompt table based on some conditions during runtime. The prompt table which is assigned to a field at runtime is called Dynamic Promp t Table. With an example we can understand easily. we have 2 views PS_SEM1_VW-- View contains first 6 months of the year PS_SEM2_VW-- View Contains next 6 months of the year. A PS_MON record have 2 fields SEMESTER MONTH Let us assume, on the page we want these 2 fields , PS_MON.SEMESTER will have 2 values -- 1st Sem and 2nd Sem If user selects "1st Sem" in PS_MON.SEMESTER field then for the second field "P S_MON.MONTH" should get first 6 months as list of prompt values. If user selects "2nd Sem" in PS_MON.SEMESTER field then for the second field "P S_MON.MONTH" should get LAST 6 months of the year as list of prompt values. To do this following steps you need to follow, Step 1: Open the Record Definition of MON Step 2: Go for the Record field properties of MONTH Field.

Step 3: Set the Property as Prompt Table with Edit Step 4: Write %EDIT1 in the Prompt table field. step 5: close it as save it. Step 6 : Now open the FieldChange peoplecode of SEMESTER and write the following peoplecode if MON.SEMESTER=1 THEN DERIVED.EDIT1=RECORD.SEM1_VW END-IF; if MON.SEMESTER=1 THEN DERIVED.EDIT1=RECORD.SEM2_VW END-IF; So now, if you save the above peoplecode and go for Portal(PS Front End,Browser) , select the "1st sem" from the SEMESTER Field , this peoplecode fires and first condition satisfies and "RECORD.SEM1_VW" will be assigned to the EDIT1 field of Derived record. As you declared the %EDIT1 as the Prompt table for MON.Month fi eld now peoplesoft understands that the as it was set as %EDIT1 in Record field properties and it is a dynamic prompt table so it takes the value which was stor ed in DERIVED.EDIT1. So , now whatever value or record name you store it in DERI VED.EDIT1 will become as Prompt table for the MON.Month field. _________________________________________________________________ Q: What are the Security Types. For example, Row Level Security, Table Level Sec urity, Field Level Security---etc. Totally, how many types are there in this abo ve. How it works in each level with explanation? A: AS PER MY KNOWLEDGE FIELD LEVEL SECURITY MEANS CONSTRAINTS LIKE UNIQUE,NOT NULL ,PRIMARY KEY.WE WILL BE GIVING THIS TYPE OF SECURITY IN DYNAMIC VIEW AND QUERY V IEW THROUGH SQL. ROW LEVEL SECURITY MEANS WE WILL BE GIVING IT IN ADMINISTRATION RULES PROPERTIE S. TABLE LEVEL SECURITY MEANS GIVING AUTHENTICATION TO THE USER. Chakravarthi +91- 9912681289 _________________________________ Try this SQL (replacing <Component_Name> with your actual component) : SELECT * FROM PSBCDEFN WHERE BCPGNAME = '<Component_Name>'

Cloning a Component Interface PeopleTools Tip Filed under: Component Interface, PeopleTools Tip

digitaleagle @ 2:00 am

Have you ever tried to recreate a component interface and allow PeopleSoft to de fault the properties and collections? The hard part is that you have to make sur e that it uses the same names as your old one or you will have to change your co de. The following SQL helped me figure how to change my code to refer to the correct fields (ex. effdt or effdt0). I was cloning the delivered CI_JOB_DATA component interface with a brand new customized component interface.

SELECT A.BCNAME, A.BCTYPE || : || A.BCSCROLL || : || A.BCSCROLLNUM || -> || A.BCSCROLL NAME LOC, A.BCITEMPARENT, A.BCITEMNAME, A.RECNAME, A.FIELDNAME, B.BCNAME, B.BCTYPE || : || B.BCSCROLL || : || B.BCSCROLLNUM || -> || B.BCSCROLLNAME L OC, B.BCITEMPARENT, B.BCITEMNAME FROM PSBCITEM A, PSBCITEM B, PSBCITEM AP, PSBCITEM BP WHERE A.BCNAME = <Old component interface name> AND A.BCNAME = AP.BCNAME(+) AND B.BCNAME = <New component interface name> AND B.BCNAME = BP.BCNAME(+) AND A.BCITEMPARENT = AP.BCITEMNAME(+) AND B.BCITEMPARENT = BP.BCITEMNAME(+) AND A.RECNAME = B.RECNAME AND A.FIELDNAME = B.FIELDNAME AND (BP.RECNAME = AP.RECNAME OR (BP.RECNAME IS NULL AND AP.RECNAME IS NULL)) AND A.BCITEMPARENT = <Parent collection name> AND A.BCITEMNAME = <Item name> Examples: <Old component interface name> CI_JOB_DATA <Parent collection name> COLL_JOB_EARNS_DIST <Item name> KEYPROP_ERNCD Chakravarthi +91- 9912681289 __________________________________________

1. to count multiple fields counts: select count(setid), count(jobcode) from ps_jobcode_tbl 2. select count(*) , count(1) from table1 ; -- this will give a count of all the records in the table 3. select count(market) , count(distinct market ), count(1) from table1; -- this will give count excluding nulls and count of distinct value s excluding nulls and count including nulls http://www.daniweb.com/forums/thread70383.html -- to delete duplicate records in table. http://www.bigresource.com/MYSQL-Multiple-COUNT-in-SELECT-statement-0t6SMovo.htm l -- for multiple counts using My SQL _____________________________________ Multiple Counts ____________________ select * from ps_jobcode_tbl select count (case when setid = 'GBL01' then 1 end )gbl01, count(case

when setid = 'USA01' then 1 end)usa01 from ps_jobcode_tbl --group by setid select count(setid),count(jobcode) from ps_jobcode_tbl select count(setid), count(distinct setid), count(1) from ps_jobcode_tbl select count(*) from (select setid, jobcode from ps_jobcode_tbl group by setid, jobcode) select count(*), count(distinct setid||jobcode) from ps_jobcode_tbl _______________________ 1. select setid, count (case when setid = 'GBL01' then 1 end )count1, count(case when setid = 'USA01' then 1 end)count2 from ps_jobcode_tbl group by setid 2. select count (case when setid = 'GBL01' then 1 end )gbl01, count(case when setid = 'USA01' then 1 end)usa01 from ps_jobcode_tbl __________________ Types of US Visa - very useful information A Visas (Official Visas) A-1: For Ambassadors, public ministers & consular officers A-2: For immediate family members of A-1 A-3: Attendants & servants of A-1 and A-2 holders B (Business/Visitor) Visa B-1 Temporary visitor for business B-2 Temporary visitor for leisure C & D Visa (For Aliens in transit) C-1,2: Alien in transit directly through US C-3: Family of C-1,C-2 in transit

C-4: Transit without Visa(TWOV) D-1: Sailors departing on vessel of arrival D-2: Sailors departing by other means E - Visa (For Traders/Investors) E-1 Treaty Trader, spouse and children E-2 Treaty Investor, spouse and children F Visa (Students) Want to study or research at a U.S. college? Then F is the visa for you F-1: Academic Student F-2: Spouse or child of F-1 H (Temporary Worker) Visa H-1B: Persons in a specialty occupation H-2B: Seasonal nonagricultural workers H-3: Trainees other than medical/academic; also training of handicaps H-4: Dependants of H visa holders I Visa (Mediapersons) Are you a reporter, film person, Editor? Then you require an I-visa Essential docs: Your press ID, a letter from the editor. J & Q Exchange Visitor Visa J-1 exchange visitors may be academics, scientists, businesspeople or students. J-1: Visas for exchange visitors J-2: Spouse or 'child' of J-1 under 21 Fiance(e) of US Citizen K-1 Fiance(e) K-2 Minor child of K-1 K-3 Spouse of a U.S. Citizen (LIFE Act) K-4 Child of K-3 (LIFE Act) Docs: Marriage certificate & Photos, Intent of marrying within 90 days in US(for K1). L Visa (Intracompany Transferees) L-1A Executive, managerial L-1B Specialized knowledge L-2 Spouse or child of L-1 Vocational and Language Students M-1 Vocational student or other non-academic student M-2 Spouse or child of M-1 O -Visa (For Prodigies) O-1: For a Genius in Sciences, Arts, Education, Business, or Athletics. O-2: Alien's (support) accompanying O-1 O-3: Spouse or child of O-1 or O-2 Athletes and Entertainers P-1: Athletes & Entertainment groups P-2: Entertainers in exchange programs P-3: Entertainers in cultural programs P-4: Spouse or child of P-1, 2, or 3 R-Visa (Religious Workers) R-1 Religious workers R-2 Spouse or child of R-1

____________________ sugandha chouksey <choukseysugandha@yahoo.com> 1/29/08 _________________