|
|
|
|
|
|
|
|
|
| Previous | Next | Contents | Index | Navigation | Glossary | Library |
If you enable the PSI client extension, the Project Status window displays the column prompts defined in the PSI Columns window and the values calculated by the extension. Because the values calculated by the client extension override values defined in the PSI Columns window, you do not need to enter a definition for a column whose value will ultimately be calculated by a client extension.
Note: If the extension returns a NULL value, the Project Status window reads the value defined in the PSI Columns window.
Running the PSI extension will degrade the product's performance; therefore define your client extensions with as narrow a scope as possible.
Print out and review the following files before you begin writing your PSI client extension. These files are located in the Oracle Projects admin/sql directory.
| PAXVPS2B.pls. | PSI Extension Package Body Template. This file contains the procedure that you modify to implement the PSI client extension. You can define as many procedures as you want within this package or within the predefined procedure. |
| PAXVPS2S.pls | PSI Extension Package Specification Template. If you create procedures outside the predefined procedure within the PA_Client_Extn_Status package, you must also modify this file to include those new procedures. |
Warning: Do not change the name of the getcols 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.
| Parameter | Usage | Type | Description |
|---|---|---|---|
| X_project_id | IN | NUMBER | The identifier of the project |
| X_task_id | IN | NUMBER | The identifier of the task. This value is set to 0 if called for the project level columns |
| X_resource_list_member_id | IN | NUMBER | The identifier for the resource. This value is set to 0 if called for project or task level columns |
| X_cost_budget_type_code | IN | VARCHAR2 | The identifier of the cost budget type displayed in PSI. This value is NULL when called from the resource status folder |
| X_rev_budget_type_code | IN | VARCHAR2 | The identifier of the revenue budget type displayed in PSI. This value is NULL when called from the resource status folder |
| X_status_view | IN | VARCHAR2 | The identifier of the status folder: PROJECTS, TASKS, or RESOURCES |
| X_pa_install | IN | VARCHAR2 | The identifier of the Oracle Projects product installed: BILLING or COSTING. BILLING includes all default PSI columns. COSTING includes all but the actual revenue and revenue budget columns. |
| X_derived_col1 through X_derived_col3 | OUT | VARCHAR2 | Three alphanumeric derived columns. Each can have up to 255 characters. Note: Column 1 refers to the first column in both the PSI Columns and the Project Status windows, Column 2 refers to the second column in each window, etc. |
| X_derived_col_4 through X_derived_col_33 | OUT | NUMBER | 30 numeric derived columns. Note: Column 4 refers to the fourth column in both the PSI Columns and the Project Status windows, Column 5 refers to the fifth column in each window, etc. |
| Table 1 - 85. (Page 2 of 2) PSI Extension Parameters | |||
| Previous | Next | Contents | Index | Navigation | Glossary | Library |