Writing the Project Security Extension (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Writing the Project Security Extension

Oracle Projects provides a template package that contains the procedure that you can modify to implement the project security extension. The name of the package is pa_security_extn, and the name of the procedure is check_project_access.

Print out and review the following files before you begin writing your project security client extension. These files are located in the Oracle Projects admin/sql directory.

PAPSECXB.pls. Project Security Extension Package Body Template. This file contains the procedure that you modify to implement the project security extension. You can define as many procedures as you want within this package or within the predefined procedure.

PAPSECXS.pls Project Security Extension Package Specification Template. If you create procedures outside the predefined procedure within the PA_Security_Extn package, you must also modify this file to include those new procedures.

Warning: Do not change the name of the check_project_access procedure. In addition, do not change the parameter names, parameter types, or parameter order in your procedure.

Suggestion: After you write the procedure, do not forget to compile it and store it in the database. See: Storing Your Procedures.

We recommend that you keep the following documentation on hand as reference material while defining procedures: the PL/SQL User's Guide and Reference Manual and the Oracle Projects Technical Reference Manual.

Package.Procedure

The following table lists the parameters that Oracle Projects provides for the project security extension, pa_security_extn.check_project_access.

Parameter Usage Type Description

X_project_id IN NUMBER Identifier of the project or project template

X_person_id IN NUMBER Identifier of the person

X_cross_project_user IN VARCHAR2 Indicates if the user is a cross-project user Y/N

X_calling_module IN VARCHAR2 Module in which the project security extension is called; Oracle Projects sets this value for each module in which it calls the security extension. The values are listed below.

X_event IN VARCHAR2 Type of query level to check upon which you can define specific rules:
ALLOW_QUERY
ALLOW_UPDATE
VIEW_LABOR_ COSTS

X_value OUT VARCHAR2 Values to specify if result of the event: Y/N

Table 1 - 100. (Page 2 of 2) Project Security Extension Parameters

Parameter	Usage	Type	Description
X_project_id	IN	NUMBER	Identifier of the project or project template
X_person_id	IN	NUMBER	Identifier of the person
X_cross_project_user	IN	VARCHAR2	Indicates if the user is a cross-project user Y/N
X_calling_module	IN	VARCHAR2	Module in which the project security extension is called; Oracle Projects sets this value for each module in which it calls the security extension. The values are listed below.
X_event	IN	VARCHAR2	Type of query level to check upon which you can define specific rules: ALLOW_QUERY ALLOW_UPDATE VIEW_LABOR_ COSTS
X_value	OUT	VARCHAR2	Values to specify if result of the event: Y/N
Table 1 - 100. (Page 2 of 2) Project Security Extension Parameters

Contents

Index

Navigation

Glossary

Library

PAPSECXB.pls.	Project Security Extension Package Body Template. This file contains the procedure that you modify to implement the project security extension. You can define as many procedures as you want within this package or within the predefined procedure.
PAPSECXS.pls	Project Security Extension Package Specification Template. If you create procedures outside the predefined procedure within the PA_Security_Extn package, you must also modify this file to include those new procedures.