This page (revision-20) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by RForbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
20 26-Nov-2021 10:22 6 KB rforbes to previous
19 26-Nov-2021 10:22 5 KB rforbes to previous | to last
18 26-Nov-2021 10:22 5 KB khiggs to previous | to last
17 26-Nov-2021 10:22 5 KB jaiken to previous | to last
16 26-Nov-2021 10:22 5 KB jaiken to previous | to last
15 26-Nov-2021 10:22 5 KB rforbes to previous | to last
14 26-Nov-2021 10:22 5 KB jmyers to previous | to last ERD-HR01 ==> ERD-HR1
13 26-Nov-2021 10:22 5 KB jmyers to previous | to last ERD-HR1 ==> ERD-HR01
12 26-Nov-2021 10:22 5 KB RForbes to previous | to last
11 26-Nov-2021 10:22 5 KB RForbes to previous | to last
10 26-Nov-2021 10:22 5 KB JAiken to previous | to last
9 26-Nov-2021 10:22 5 KB RForbes to previous | to last
8 26-Nov-2021 10:22 5 KB RForbes to previous | to last
7 26-Nov-2021 10:22 5 KB RForbes to previous | to last
6 26-Nov-2021 10:22 5 KB RForbes to previous | to last
5 26-Nov-2021 10:22 5 KB RForbes to previous | to last
4 26-Nov-2021 10:22 5 KB RForbes to previous | to last
3 26-Nov-2021 10:22 5 KB RForbes to previous | to last
2 26-Nov-2021 10:22 5 KB JAiken to previous | to last
1 26-Nov-2021 10:22 5 KB RForbes to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
Derived columns can be added to tables, to further extend their utility, deriving their value from a PL/SQL function in the data base. This allows the field to be displayed on other screens as a display-only value.
Derived columns can be added to tables, to further extend their utility, deriving their value from a PL/SQL function in the data base. This allows the field to be displayed on screens as a display-only value.
At line 4 changed one line
The function must be defined in the data base as a PL/SQL function. The PL/SQL function must receive exactly one parameter: the ID of the record from the table the field is associated to; And the function must return a value (or NULL) of the type that is expected by the screen.
The function must be defined in the data base as a PL/SQL function. The PL/SQL function must receive exactly one parameter: the ID of the record from the table the field is associated to; And the function must return a value (or NULL) of the type that is specified in IMCD.
At line 8 changed one line
* The function name __should NOT__ start with P2K_ so as to preclude any confusion about its source (P2K_xxxx is reserved for High Line).
* The function name __should NOT__ start with P2K_ so as to preclude any confusion about its source (P2K_xxxx is reserved for those supplied with the application).
At line 14 changed one line
In this example it is desired to have a column showing the value of a statistic called (seen on [IMST]) for an employee. By reviewing the [ERD|ERD-HR1] for the [P2K_HR_STATISTICS] table we can see that the record is identifiable as an intersection between [EEM_ID] (The ID from [P2K_HR_EMPLOYMENTS]) and [DSC_ID] (The ID from [P2K_CM_STATISTIC_COMPONENTS]). As we know the specific statistic code we will always want, we can determine that the variable element here is the employment record ID.
In this example it is desired to have a column showing the value of a statistic called STAT-PA-DAYS (seen on [IEST]) for an employee. By reviewing the [ERD|ERD-HR1] for the [P2K_HR_STATISTICS] table we can see that the record is identifiable as an intersection between [EEM_ID] (The ID from [P2K_HR_EMPLOYMENTS]) and [DSC_ID] (The ID from [P2K_CM_STATISTIC_COMPONENTS]). As we know the specific statistic code we will always want, we can determine that the variable element here is the employment record ID.
At line 46 changed 2 lines
Once we have the function defined and working, we can extend the table (in our example [P2K_HR_EMPLOYMENTS]) to include this User Formula Column. This is done in the [IMCD] screen by adding a new co9lumn with the following fields filled in:
;[Sequence]:It is recommended that you start your sequencing at 9999 and work down, so as to not collide with High Line provided sequence numbers
Once we have the function defined and working, we can extend the table (in our example [P2K_HR_EMPLOYMENTS]) to include this User Formula Column. This is done in the [IMCD] screen by adding a new column with the following fields filled in:
;[Sequence]:It is recommended that you start your sequencing at 9000 and work down, so as to not collide with High Line provided sequence numbers
At line 51 changed one line
;[Data Type|DATA_TYPE]: Must of the the same type that the function returns (Number, Date, Varchar2)
;[Data Type|DATA_TYPE]: Must be the same type that the function returns (Number, Date, Varchar2)