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

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

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
22 26-Nov-2021 10:22 26 KB kparrott to previous
21 26-Nov-2021 10:22 26 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
Training.Create_Winward_Report...nobody
Training.Create_Winward_Report

Version management

Difference between version and

At line 106 changed one line
#Open IMFDH and edit the Form Layout tab of the REBR function.
#Open IMFDH and edit the Form Layout tab of the REBR function.\\ \\[Training.Create_Winward_Report_04.jpg]\\ \\
At line 108 changed 3 lines
This will require the user to manually key in the two digit month in order to run the report. By making a simple change to the parameter defined in IMPM, a lexicon list can be offered to the user to select the month or months to report.
ADD A LEXICON FOR PARAMETER SELECTION
In IMPM, for the P_MONTH parameter of REBR, replace the VARCHAR2 in the Reference column with X_REG_EMPLOYMENT_DATE.
This will require the user to manually key in the two digit month in order to run the report. By making a simple change to the parameter defined in IMPM, a lexicon list can be offered to the user to select the month or months to report.
!!Add a Lexicon for Parameter Selection
In [IMPM], for the P_MONTH parameter of [REBR], replace the VARCHAR2 in the Reference column with [X_REG_EMPLOYMENT_DATE].\\ \\
At line 112 changed one line
DEPARTMENT HEAD COUNT
!!Department Head Count
At line 114 changed 12 lines
Start by opening the IMFN screen and selecting the RENA report.
In the lower portion of the screen, click on the Copy Function and Form button. This will display another dialog with a new function name suggested.
Since our report will not 'extend' the RENA report, change the function name to REHC to represent Report Employee Head Count.
Leave the checkmark turned on for Copy as User Defined and press OK.
Once the new function has been created, select it in IMFN and remove RENA from the Extends field. Failing to remove this entry will cause any user running RENA to run our report instead. The new function will have a new set of tables defined in IMFDH, as well as a form layout definition. All the parameters will have been copied to our new function and a report list query created on IMLQ. If needed, any of these screens can be edited to alter the report to our needs. For this example we will leave them unaltered.
Open MS Word and created a new RTF file that matches our new function name, REHC.rtf. Again, ensure that the file name is in uppercase while the extension is lowercase. Both ePersonality and the Windward report engine are case sensitive when it's looking for the report template file.
In the Auto Tag menu, define the data source for our new report:
http://argo.highlinecorp.com/selfService_AS01/reportdatastructure?NAME=REHC
Again, this is only an example. Both the application server and Self Service instance name will need to be changed to a local environment.
The Windward report engine does not contain any functions or tags to generate totals in a report. Instead, the template will need to track the records that are processes and display these totals as they're needed. It will also need to reset one counter and start counting again during control breaks. Counters can be created anywhere in the template before looping through the data with a FOREACH tag. A SET tag is used to define a variable name and give it an initial value. A nickname is also suggested for these tags. This report will need two SET tags, one for the department total and a second for the grand total.
The entire report will be displayed in a table, five rows long by three columns wide.
Above a 3x5 table add two SET tags from the Tags drop down menu of the Auto Tag rib¬bon. One named 'setGT' with a variable name of GrndTotal and second named 'setDT' with a variable name of DeptTotal, both with a value of 0. These variables will be used later to count the number of records processed.
#Start by opening the IMFN screen and selecting the RENA report.
#*In the lower portion of the screen, click on the Copy Function and Form button. This will display another dialog with a new function name suggested.
#*Since our report will not 'extend' the RENA report, change the function name to REHC to represent Report Employee Head Count.
#*Leave the checkmark turned on for Copy as User Defined and press OK.
#Once the new function has been created, select it in IMFN and remove RENA from the Extends field. Failing to remove this entry will cause any user running RENA to run our report instead. The new function will have a new set of tables defined in IMFDH, as well as a form layout definition. All the parameters will have been copied to our new function and a report list query created on IMLQ. If needed, any of these screens can be edited to alter the report to our needs. For this example we will leave them unaltered.
#Open MS Word and created a new RTF file that matches our new function name, REHC.rtf. Again, ensure that the file name is in uppercase while the extension is lowercase. Both ePersonality and the Windward report engine are case sensitive when it's looking for the report template file.
#In the Auto Tag menu, define the data source for our new report:\\[http://argo.highlinecorp.com/selfService_AS01/reportdatastructure?NAME=REHC]\\ \\Again, this is only an example. Both the application server and Self Service instance name will need to be changed to a local environment.\\ \\The Windward report engine does not contain any functions or tags to generate totals in a report. Instead, the template will need to track the records that are processes and display these totals as they're needed. It will also need to reset one counter and start counting again during control breaks. Counters can be created anywhere in the template before looping through the data with a FOREACH tag. A SET tag is used to define a variable name and give it an initial value. A nickname is also suggested for these tags. This report will need two SET tags, one for the department total and a second for the grand total.\\ \\The entire report will be displayed in a table, five rows long by three columns wide.
#Above a 3x5 table add two SET tags from the Tags drop down menu of the Auto Tag rib¬bon. One named 'setGT' with a variable name of GrndTotal and second named 'setDT' with a variable name of DeptTotal, both with a value of 0. These variables will be used later to count the number of records processed.
At line 127 changed 4 lines
Also above the 3x5 table, create the first FOREACH tag. In the sample template this loop is named 'eachDEN' with a variable name of DEN. Ensure the following item is selected for the tag:
/Data/EASD/EAS_ID/EEM_ID/DEN_ID/ENTITY_CODE
The first cell of the first line will contain the entity code label and an OUT tag for this data. Ensure the item that is being displayed is the ENTITY_CODE from /Data/EASD_ID/EEM_ID/ DEN_ID. This is the entity code associated to the employee.
In each of the cells of the second row, enter the column headings for the report; Department Code, Department Name and Count. The third row will be left blank to provide space between the headings and the data.
#Also above the 3x5 table, create the first FOREACH tag. In the sample template this loop is named 'eachDEN' with a variable name of DEN. Ensure the following item is selected for the tag:\\ \\/Data/EASD/EAS_ID/EEM_ID/DEN_ID/ENTITY_CODE\\ \\The first cell of the first line will contain the entity code label and an OUT tag for this data. Ensure the item that is being displayed is the ENTITY_CODE from /Data/EASD_ID/EEM_ID/ DEN_ID. This is the entity code associated to the employee.\\ \\
In each of the cells of the second row, enter the column headings for the report; Department Code, Department Name and Count. The third row will be left blank to provide space between the headings and the data.\\ \\
At line 132 changed one line
/Data/EASD/DDP_ID/DEPARTMENT_CODE
/Data/EASD/DDP_ID/DEPARTMENT_CODE\\ \\
At line 134 changed 8 lines
The first is an OUT tag to display the department name. This item is located under the DDP_ID/ID item in EASD: /Data/EASD/DDP_ID/ID/DEPARTMENT_NAME.
After the OUT tag another FOREACH is needed to loop through all the assign¬ment details associated to this department: /Data/EASD.
Inside this loop the variables defined at the top of the template will need to be incremented. This is done with another pair of SET tags. These two tags can have new nicknames to identify them but must have the same variable name defined for the original SET tags. Also they will contain an expression instead of a value. The expression to increment the DeptTotal is: ${DeptTotal}+1, while the expression to increment the GrndTotal is: ${GrndTotal}+1.
Finally we close this loop with and END tag.
The last cell of row four is used to display the value of the department counter. Add an OUT tag and select the new item named ‘DeptTotal’.
The last row of the 3x5 table is used to rest the department counter, end all the loops and display the grand total of the report.
In the first cell add another SET tag with a value of 0 and a variable name of DeptTotal. Since this is after the count has been displayed and before it processes the next department, it will need to be reset to zero again. Also in this cell both loops need to be closed. Create two END tags, one for the department loop and one for the entity loop.
The second cell of row five simply contains the table for our grand total, while the last cell contains an OUT tag for this total.
*The first is an OUT tag to display the department name. This item is located under the DDP_ID/ID item in EASD: /Data/EASD/DDP_ID/ID/DEPARTMENT_NAME.
*After the OUT tag another FOREACH is needed to loop through all the assign¬ment details associated to this department: /Data/EASD.
*Inside this loop the variables defined at the top of the template will need to be incremented. This is done with another pair of SET tags. These two tags can have new nicknames to identify them but must have the same variable name defined for the original SET tags. Also they will contain an expression instead of a value. The expression to increment the DeptTotal is: ${DeptTotal}+1, while the expression to increment the GrndTotal is: ${GrndTotal}+1.
*Finally we close this loop with and END tag.\\ \\
The last cell of row four is used to display the value of the department counter. Add an OUT tag and select the new item named ‘DeptTotal’.\\ \\
The last row of the 3x5 table is used to rest the department counter, end all the loops and display the grand total of the report.\\ \\
In the first cell add another SET tag with a value of 0 and a variable name of DeptTotal. Since this is after the count has been displayed and before it processes the next department, it will need to be reset to zero again. Also in this cell both loops need to be closed. Create two END tags, one for the department loop and one for the entity loop.\\ \\
The second cell of row five simply contains the table for our grand total, while the last cell contains an OUT tag for this total.\\ \\
[Training.Create_Winward_Report_05.jpg]\\ \\
The following two images show sample output from this report when run from ePersonality.\\ \\
[Training.Create_Winward_Report_06.jpg]\\ \\
[Training.Create_Winward_Report_07.jpg]
At line 143 removed one line
The following two images show sample output from this report when run from ePersonality.
At line 145 changed 2 lines
MODIFYING A WINDWARD REPORT
!!Modifying a Winward Report
This page (revision-22) was last changed on 26-Nov-2021 10:22 by kparrottTop