Author Archives: gvr4wd

Unknown's avatar

About gvr4wd

...hmmm

Dong Shin 08.29.2014

  • added new contract (not COGNOS) and invoice tabs to RA
  • working on Monthly Data Status
    • new query to get status for FA (RequisitionsView.mxml)
      • SELECT IF(ISNULL(oo.month_1), ‘OVERDUE’, ‘CURRENT’) AS status, bc.* FROM budget_centers bc LEFT JOIN obligations_outlays oo ON oo.funding_id = bc.uid WHERE oo.type LIKE ‘PM Actuals%’ AND oo.year + oo.year_count – 1 = 201) AS t LEFT JOIN __view_committed_totals AS ca ON t.uid = ca.budget_center_id LEFT JOIN projects AS p ON t.project_id = p.uid GROUP BY t.uid ORDER BY t.uid

Dong Shin 08.28.2014

  • change the status in RA to look at PM Actuals (18th is the cut off day)
  • remove DFAS Paid from invoice…
  • working on adding contracts in RA – done
    • asks to add when there is no contracts, asks to complete if contract is incomplete
  • working on adding contracts/invoice tab in RA

Dong Shin 08.27.2014

  • deployed new FA/RA with contract/invoices and lab… not quite working right
    • Fix field changing bug caused by addition of Lab.
    • Lockdown baseline rows so only Admin’s can edit them.
    • Contracts Tab: Use the same fields from Funding Request Form from Contract Details button (Contract Name to Place of Performance)
    • Invoice Tab: Contract Number and ACRN pulled from COGNOS and delete Date DFAS Paid
    • When open a req for financial data entry Contracts pop-up.
    • Move View FMP Button and View Invoices Button to tabs in RA.
  • working on new contracts format…. new from Funding Request Form
    • Structure
      • Contract Name: If these funds will be placed on a contract enter the contract name of that contract.
      • Contract Number: If these funds will be placed on a contract enter the contract number of that contract.
      • Contract PoP Start: If these funds will be placed on a contract enter the contract PoP start date.
      • Contract PoP End: If these funds will be placed on a contract enter the contract PoP end date.
      • COR Name: If these funds will be placed on a contract enter the name of the COR of the contract.
      • COR Email: If these funds will be placed on a contract enter the email address of the COR of the contract.
      • COR Phone: If these funds will be placed on a contract enter the phone number of the COR of the contract.
      • Vendor: If these funds will be used to fund contractor labor, material or travel enter the name of the contractor.
      • Place of Performance: If these funds will be used to fund contractor labor, material or travel enter the place of performance of the contractor.
    • created contracts table….

Dong Shin 08.26.2014

  • grails experiment – 2.3.1
    • changed generated class names to singular – use table in static mapping
    • relation working – make sure ID fields are named correctly
    • got XML/JSON server working – replace json with xml to get xml response
      • /project.json to get a list JSONized
      • /project/index to get an HTML standard scaffolding
      • /project/create.html scaffold for a new item
      • /project/show/1.html scaffold edit item 1
      • /project/show/1.json JSON for item id: 1

Dong Shin 08.22.2014

  • set budget centers data in Contracts and Invoices tabs in the Update Requisition Data so that correct related data are retrieved
  • added data counters to Contract and Invoices tabs
  • working on adding Labs to Requisition Data
    • added labs table, ‘TBD’ for temporary row
    • added lab column in budget_centers table
    • added lab to Update/Add Requisition Data panel
    • added insert/update code

Dong Shin 08.19.2014

  • deployed new FA/RA, database updates to the test server….
    • need to changed the 3, 4 year queries – done
  • working on adding invoices and contracts tabs
  • challenging SQL problem from Phil
    • update comments in fr_master_table with value from fr_text_table where the comments don’t contain value…
    • UPDATE fr_master_table f SET comments = CONCAT(
      IF(ISNULL( (SELECT value FROM (SELECT ftt.value, fmt.uid as uuid FROM fr_master_table fmt RIGHT JOIN fr_text_table AS ftt ON ftt.uid
       LIKE CONCAT(‘%’,fmt.uid, ‘_taskName’) AND fmt.comments NOT LIKE CONCAT(‘%’, ftt.value, ‘%’)) AS X WHERE f.uid = X.uuid)), ”,

      CONCAT(‘Task ID: ‘, (SELECT value FROM (SELECT ftt.value, fmt.uid as uuid FROM fr_master_table fmt RIGHT JOIN fr_text_table AS ftt ON ftt.uid LIKE CONCAT(‘%’,fmt.uid, ‘_taskName’) AND fmt.comments NOT LIKE CONCAT(‘%’, ftt.value, ‘%’)) AS X WHERE f.uid = X.uuid), ‘ – ‘)),
      comments);

Dong Shin 08.14.2014

  • continue working on adding Baseline rows
    • query to fix Procurement (year 3 and 4) RDT&E (year 3) not showing in Obligations/Outlays, this  must be done prior to adding baseline rows.
      • INSERT INTO obligations_outlays_fix (type, project_id, funding_id, year, year_count)
        SELECT ‘Planned Obligated $:’, p.uid, c.uid, c.fiscal_year, 3 FROM projects p LEFT JOIN budget_centers c ON p.uid = c.project_id
        WHERE appropriation LIKE ‘RDT&E%’;
  • working on adding not 100% obligated to Overdue Obligations query – line item 13
  • wordpress post editor has been changed! arghhh! hating it!

Dong Shin 08.12.2014

  • working on adding Planned Baseline rows
    • added Planned Obligation Baseline: and Planned Outlay Baseline: to obligation_outlay_types table
      • INSERT INTO `project_portfolio_enh`.`obligation_outlay_types` (`uid`, `type`, `visible`, `status`) VALUES (NULL, ‘Planned Obligation Baseline:’, NULL, NULL), (NULL, ‘Planned Outlay Baseline:’, NULL, NULL);
    • add Planned Obligation/Outlay Baseline rows for existing data
      • INSERT INTO obligations_outlays
        (type, year, year_count, project_id, funding_id)
        (SELECT ‘Planned Obligation Baseline:’, year, year_count, project_id, funding_id FROM `obligations_outlays`
        GROUP BY funding_id, year_count) UNION ALL
        (SELECT ‘Planned Outlay Baseline:’, year, year_count, project_id, funding_id FROM `obligations_outlays`
        GROUP BY funding_id, year_count);
    • update visible in obligation_outlay_types so only Admins and NSA PM’s can see the planned baseline rows
      • UPDATE obligation_outlay_types SET visible = 0;
        UPDATE obligation_outlay_types SET visible = 1 WHERE type <> ‘Planned Obligation Baseline:’
        AND type <> ‘Planned Outlay Baseline:’;
    • added visible flag to getFinancialData
  • back up current database – project_portfolio_enh_081214, cleaned up databases….

Dong Shin 07.28.2014

  • deployed new FA with Req’s by Project queries
    • found that Query Builder adds where and group by clause – fixed
    • not saving queries – fixed
    • percent values should be calculated using Total Budgets, not Committed Amounts  – fixed
  • working on summarizing obligations, outlays, pm actuals for Req’s by Project queries