Spreadsheet: sally_beck__33741__Showstopper_Status
Sheet: Showstoppers

ENERGY OPS - SETTLEMENTS/VM REPORT LIST
[NAME]
2000-08-14 00:00:00
REPORT NAME | REPORT TYPE | MENU PATH | ENA ISSUES | COMMENTS/UPDATE | ACTION ITEMS (AI) & RESULTS (R)
#1-The Matrix-Transaction Detail  Needed 8/1 (pending Troy K's agreement) | Custom | Accounting\Enterprise Controlling\Profit Center Accounting\Information System\Report Selection\ENA Matrix Report\ENA Matrix Report Selection paramaters should be Period 8, Company 0364.  Leave profit center blank. |  |  | R:  The Matrix-Detail report will likely be developed in BRIO, the new data warehouse program. (August/September)
#2-G/L Line Item Report (GL 110)  Complete | Standard | Accounting\Financial Accounting\General Ledger\Periodic Processing\Information System\Report Selection\ Information System\Account Information\Line Items | Manual work needed to present data to management.  Report wraps one line item to the following line. | Can't change standard report format (wrapping)  - use the GL extract report. | None
 |  | Accounting\Financial Accounting\General Ledger\Account\ Display Line Items (use variant) | none | Per 6/14 phone conversation with Gary/Rhonda/Juan, instructed user to click on additional field icon and choose quantity field and included that column in the report.  Report does not wrap. Custom layout was created that is suitable for users. | None
#3-Unify A/R Cash Flow Report (Apache Report)     (Needed 8/1) | File Upload to Excel, Run Report In Access | Accounting\Financial Accounting\Accounts Receivable\ Periodic Processing\Information System\Report Selection\ Other Analyses\Account\Line Items. |  | Because the e-credit rating is not available in SAP, a report will be created in access, using the unconverted file format & the Line Items Report.    The tax department agreed that separation of netting and cash receipts activity was not necessary, making the report less difficult to design. | R: [NAME].
#4-Unify vs SAP I/C Compare Report (Needed 7/5) | Unify Report | In production environment: In Settlements--> Report->Accounting Transactions->Intercompany [NAME]. |  |  | R:  The Unify vs. SAP Intercompany Reconciliation Report is currently in production. A follow up meeting occurred 8/10 .  After the latest improvements were made on 8/10 (in stage) the only outstanding issue is:  the ability to filter by transaction type (sales vs. service).  Statistical order number is now available on the report.  All of the latest changes will be in the production environment on 8/14.  Additionally, the report displays only unpaid items and the statistical order number is now available on the report.
#5-A/R and A/P Aging                            (Needed 7/5) | Standard | Accounting\Financial Accounting\Accounts Receivable\ Periodic Processing\Info System\Select Report\Information System\Account Information\AR Analysis - Energy Ops | (1)  A custom report is necessary because of the following items:  The standard report sorts by profit center. Multiple search options are not acceptable for long term use because information needs to be presented in more ways than can be achieved through SAP functionality. (example: viewing ENA deals for Texas business only). [NAME] suggested utilizing an external table that SAP can reference for running reports by coordinator or regional responsibilities.  In addition, settlement period is not displayed on any custom A/R report, and the output to excel is not in a useable format for frequent analysis.  (2) Need to design processes for the xref2 field to be manually populated for netting and cash application functions where SAP generates the document.  This is necessary  to display all open items for a subledger account when using report variants that pull data based on the xref2 field contents. (3) Need automatic population of xref2 field in SAP generated documents post 7/1. | Custom reports were developed  (3) The Apollo team has not found a solution to the xref2 problem.  Their solution is to have the users develop custom reports that pull data based on relationships using the parent/child documents. This method would retrieve the information that does not carry forward when SAP generated documents are created, but it requires an ABAP programmer to write each report. [NAME] is on the data warehouse (BRIO) team and will explore options for viewing information  using the warehouse. More information will be available as the project comes together. | R:  (1) Currently, the report cannot be backdated to present information as of a past date, such as GL close.   [NAME] contacted the COE and requested enhancements for the AP & AR reports for the previously mentioned date problem,  for making header data more concise, and for retrieving production date from the text field (for gas needs).  The COE  wrote 3 remedy tickets for the AR items and is in the process of creating tickets for the AP items. The programmer has corrected  the backdating functionality but not the production month/text field item in the AP report.  Testing done by [NAME] and [NAME]  indicates the backdating report change is working correctly.  [NAME] left a message for [NAME] requesting the report be moved to QA.  AI: [NAME] to tell [NAME] when the AP report changes can be moved to the QA environment and when the [NAME] report can be changed (and tested) in the development environment.
#7-Past Due A/R Invoices > 60 Days Exluding Invoices Prior to 1/30/99 (for insurance policy)   (Needed 8/1) | ZCASH | Accounting\Enron Enhancements\Accounts Receivable\ Cash Management\Accounts Receivable\Customer Invoices\Invoice - [NAME] | (1) Need xref2 field populated automatically for SAP generated transactions. | .Manual processes and procedures have been developed to populate xref2 for SAP generated transactions. | R: Complete.   Instructions  for retrieving this information  from SAP were sent to everyone who provides this data to [NAME].
#16-Cash Forecast Report ([NAME])  (Needed 7/5) | ZCASH | Accounting\Enron Enhancements\Accounts Payable\Cash Management\Accounts Payable\Cash Flow\Accounts Payable\By Expected Date \Cash Flow by Commoduty Type |  | This report is complete but does not contain the correct data because upstream users cannot identify blocked items and, as a result,  cannot accurately forecast.  Enhancements requested in the report views in #17 Forecasted Invoices by Expected Date will allow the data to be fixed upstream so this report (#16 Cash Forecast Report) will display the correct information. | R: The programmer said the requested changes are made.  Testing the new payment block and expected amount is expected to begin 8/15.  AI:  [NAME] and [NAME] will test the changes in the QA environment.
#17-Forecasted Invoices by Expected Date  (Needed 7/5) | ZCASH | Accounting\Enron Enhancements\Accounts Payable\Cash Management\Cash Flow\Accounts Payable\by customer namecustomer number/coordinator | Need to have current reporting views modified to display payment block & expected date. |  | R: The programmer said the requested changes are made.  Testing the new payment block and expected amount is expected to begin 8/15.  AI:  [NAME] and [NAME] will test the changes in the QA environment.
 |  |  | VERY HIGH PRIORITY REPORTS:
AP Load Report / Pay Entity Report |  | Accounting / Financial Accounting / Accounts Payable/ Periodic Processing / Select Report / Enron Specific Reports / Pay Entity Report              (Pay entity is 0530, enter company number & date range) | Currently, the date shown in this report is the date the payment program was run.   Settlements and Treasury need to see the date the payment was sent from the bank.  This is needed both for cash control and payment research. |  | R: The payment date (actual date a wire was sent & actual date a check was cut) and the xref 2 were added to the report.  AI: Alysia is  testing the report in production with live data and will reconcile with Treasury workstation.  Alysia will share her results with [NAME], [NAME] and Pam so we can determine where discrepancies (if any) occur.