Monday, June 25, 2012

Urgent Cognos Developer Need in OH, In-person Interview, no phone interview, Rate: $55/hr


Dear Friends,

Please send only locals or who can attend F2F, No phone interview.

\ Interviews - in person - scheduled for 6/28 and 6/29

Duration: 7/9/12 - 1/4/13

Cognos Business Intelligence Reports Developer will be utilized in migrating and upgrading the over 200 Cognos reports and, cube functions to the currently supported version levels. Upgrade cubes from Cognos 7 to Cognos 8 using Cognos Transformer. Use existing Impromptu reports to validate reports that have been upgraded or re-designed using Report Studio. Test cube and drill-through report functionality in Power Play Web. Document and analyze business and system requirements. Perform data analysis to understand the structure & content reporting data. Write and optimize complex SQL code and stored procedures. Design, develop, implement and assist in validating Framework Manager models and Cognos report code. Develop complex Framework Manager models and Cognos report code. Create and execute unit test plans based on system and validation requirements. Troubleshoot, optimize and tune Framework Manager models and Cognos report  processes. Document all report development related work per company's methodology. Maintain existing code and fix bugs when needed. Ensure all schedules for cube builds and report delivery are met. Self-manage time and task priorities to meet project timelines and identify potential project risks. Manage multiple work assignments and junior consulting staff to meet project timelines. Create/submit weekly projects status reports and timesheets.

 

The upgrade of JFS Cognos 7.4 software to Cognos 8.4 will be performed using the following Cognos tools and methodology:

 

.             Impromptu,

.             Transformer

.             Powerplay

.             Framework Manager

.             Report Studio. 

 

Cognos upgrade Development Methodology:.

 

1.            Updating the FM model conversion to C8 (Use the FM model from the migration result set above)

a.            Verify the model .

b.            Resolve any errors and warnings in the model.

c.             Remove the schema name "WF50PP" from the datasource.   (This will default the datasource to use WFDW01DP which is preferred by the DBAs)

d.            Defining appropriate properties for date or numeric query items and aggregation properties.

e.            Resolve relationship loops by creating alias shortcuts.

f.             Create prompt filters for all dimensions and their in the cubes to be used in Drill through reports.

g.            Create any calculations and filters used in the multiple reports.

h.            For all OFAM or OHP projects, create new County and Collaborate security filters (wherever appropriate) using the new roles to replace the existing 88 county filters.  Follow the instructions in County Security setup documentation.

i.              Save and Publish the package.

 

2.            Upgrading  a Cognos 7.4 cube with Cognos 7 catalog to Cognos 8.4 cube

a.            Upgrade all iqd.imr reports from Cognos 7 to Cognos 8 using Cognos migration tools.

b.            Test the reports to make sure they have no errors, resolve errors if any.

c.             Match the SQL generated by the reports to .IQD files in the older version.

d.            Open the existing pyi using Transformer 7.4 and save as a .mdl.

e.            Open the .mdl file using Transformer 8.4

f.             Right click on each IQD, Change Source Type/Reports and select the report that matches the IQD.

g.            After an error message, selecting "Yes" displays Query definition, where query items in the package should be matched with the query items in iqd datasource.  Validate and save for each iqd.

h.            Redefine location for any .csv files.

i.              Delete the Sign On.

j.             For each measure modify the drill through reports to use .crr report instead of .imr.

k.            Validate the Transformer model

l.              Set the location for .mdc and build the cube with the new model.

m.           Publish the .mdc using current version of PPES to the desired location with same process as before.

n.            Set up the drill through location in PPES and enable Drill through Assistance.

o.            Publish and test the cube in BIDEV.

 

3.            Setup drill through reports

a.            Select different dimensions and levels to filter and with Drill through assistance enabled.

b.            Create prompt filters for drill through reports in the model to match the prompts in drill through assistance.

c.             Save and Publish the package.

d.            Add the prompts to each Drill through report query and make them optional.

e.            Save the report without the .imr in the extension and naming standard (The name should match the report name specified in the Transformer model/ drill through)

f.             Test the cube to report drill through for each level and dimension.

 

4.            Converting promptable reports

a.            Open the migrated .imr report in Cognos 8.4.1 Report Studio

b.            Validate the report to make sure there are no errors.

c.             Run the report in Cognos 7.4 in BIC.

d.            Run the report in Cognos 8.4 in BIDEV.

e.            Compare the output of the two reports.

f.             Obtaining the Cognos 8.4 report template from the BIC Developers, incorporate this look and feel in the new Cognos 8.4 report migrated.

g.            Create singleton objects in the report heading to display certain parameters that should be placed in the heading of the report.

h.            Place a text item within the singleton object and display the data item value of the field you want to place in the header of the report.

i.              To prevent rounding from occurring within the Average Days in Locate summary within the heading, average rounds automatically when 0 decimal places are rendered. To avoid this, calculate the ABS (absolute value) of the average summary.

j.             Place all of the header report variables and text boxes neatly within a table object.

k.            Create a Section header in the report for the County column

l.              Format the column borders to look like a Cognos 8.4 report instead of what is originally done in Cognos 7.4 (Old look and feel of the report still exists even though the report was migrated to Cognos 8.

m.           Run the report once again for final testing purposes.

n.            Save the final copy of the report.

 

5.            Upgrading a Cognos 7.4 cube with Cognos 8.4 FM model  to Cognos 8.4 cube

a.            Open the FM 8.4 model with IQD query subjects, change the Externalize Method property from IQD default on IQD Query Subjects.

b.            Publish the IQD package to BIDEV.

c.             Open the existing pyi using Transformer 7.4 and save as a .mdl.

d.            Open the .mdl file using Transformer 8.4

e.            Right click on each IQD, Change Source Type/Package and select the IQD package

f.             After an error message, selecting "Yes" displays Query definition, where query items in the package should be matched with the query items in iqd datasource.  Validate and save for each iqd.

g.            Redefine location for any .csv files.

h.            Validate the Transformer model

i.              Set the location for .mdc and build the cube with the new model.


Regards

Ram

sram@smart-itstaffing.com





--
You received this message because you are subscribed to the Google Groups "SureShotJobs" group.
To post to this group, send email to sureshotjobs@googlegroups.com.
To unsubscribe from this group, send email to sureshotjobs+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sureshotjobs?hl=en.

No comments:

Post a Comment