Spreadsheet: sally_beck__33723__ENERGY_OPS_000629
Sheet: Showstoppers

ENERGY OPS - SETTLEMENTS/VM REPORT LIST
[NAME]
2000-06-23 00:00:00
REPORT NAME | REPORT TYPE | MENU PATH | [NAME] | 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 Your selection paramaters should be Period 8, Company 0364.  You can leave profit center blank. | Matrix Report.                                                                                                        Matrix Detail Report. | Users to first become comfortable with the summary report and then will pursue a detailed report. | Report is currently in development.  The current plan is to bring in the PCA line item, special ledger information (settlement period) and Vendor/Customer Master Data into Excel and run VLOOKUP functions to create a report that includes all fields required by user by 6/29. | R: Settlements and OA group users viewed the summary matrix report in SAP. AI: [NAME], [NAME], and [NAME] to work with the report and to review the accuracy of profit center mapping.
#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 | None - Accepted by Business Unit 6/23 | 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 - Accepted by Business Unit 6/23 | 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. | A/R Line Item Flex File Upload - Done | E-Credit rating not available in SAP. | Send A/R line item report  from SAP to Access and add in the E-Credit information.  Sent test A/R file extract to [NAME] on 6/15.  Also categorized document types by Invoice, Netting and Cash Application to be used for the report columns. | R:  [NAME] is working on the access report using the flat file format from SAP.  Excel cannot accommodate the spreadsheet format when the number of line items in the SAP report exceed 65,000.   [NAME] said he is making steady progress. AI:  [NAME], [NAME], and [NAME] to communicate and  resolve outstanding items as they are identified.
#4-Unify vs SAP I/C Compare Report (Needed 7/5) | Unify Report | N/A | None | Need various subtotals added to report, need variances supressed on mcf volumes, and need draft items added to the unify side of the report.  Various formatting and header changes requested also. | N/A | R:  [NAME] has communicated the ENA issues to the unify programmers. Revised reports with user requested features are available for review 6/23.  AI:  Users to review the report format and data and provide feedback to [NAME].
#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/AP Aging Report |  | (1) xef2 field will be populated for data converting from MSA (2) A/P A/R Aging sorts by profit center and is awkward to use. (3)  The multiple search options that exist with dynamic selections and variants  are a workable option for 7/1 but do not provide the flexibility requested for long-term use (such as viewing data by profit center/region). [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.  (4) Need to design processes for the xref2 field to be 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. (5) Need a report to identify sap generated transactions without data in the xref2 field (6) Residual (netting) transactions have been identified as not having the ability to store xref2 information. A programming change is needed. | (1) see results section (2) no way to prevent report from sorting by profit center per [NAME] (3)  Multiple search options will work temporarily. It is not acceptable for long term use of the report 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] and [NAME] discussed the possibility of having unify populate the text field in the A/P and A/R records with the settlement period. Many changes would have to be made for this to work.  (5) A report has been identified that will display only the documents missing data in xref2 field. | R:  Tech spec with settlement's requirements was approved by [NAME] and forwarded to [NAME]. Emitra's response to the spec was ,"At this time we are not doing an additional custom report, because the AP/AR aging report currently being tested has the information requested that can be retrieved from AP/AR." Emitra asked [NAME] to review the current report options with Energy Ops and to determine what needs to be done from there. [NAME], Emitra. [NAME], [NAME], Pam and [NAME] met 6/23 and discussed reporting needs and feasability of the tech spec.  (6) Rena initiated the programming spec change to have xref2 present in residual transactions. The spec was approved. and  the change made. AI:  (1) Kris to test data in the xref 2 field after the interface occurs. [NAME] left message with [NAME] to arrange a time to view interface results. (3)Rainier, Emitra, and [NAME] are looking into how to provide settlement period (production month) information on the report. (4) Kris to research the process necessary to populate xref2 field for SAP generated documents. Pam and [NAME] to implement processes to populate xref 2 in netting and cash application procedures.(6) Rena to test the results of the spec change that will allow residual transactions to store xref2 data.
 |  | Accounting\Financial Accounting\Accounts Receivable\ Periodic Processing\Info System\Select Report\Information System\Account Information\Days Overdue Analysis (same report/path available in Accounts Payable section). | Breakdown of AB document type by commodity type.                      Settlement Period - per Business Unit Spec dated 6/21.                 Profit Center (new business unit requirement-new report). |  | Use summarization level #6 for best format.  User can define overdue dates.  Use search term criteria to pull customer/vendors by name (A to AZZZZZ for A vendors).  Save variant specific to responsibilities. | and cash application procedures.(6) Rena to test the results of the spec change that will allow residual transactions to store xref2 data and let [NAME] know the results on 6/26.
#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] | Invoice Flex File from ZCASH - done. | (1) xref2 field needs to be populated for data converted from MSA (2) research needed to determine how best to populate xref2 in sap generated documents |  | R:  (1) xref2 to be populated in MSA data conversion. AI:   (1) Kris to observe MSA interface results 6/23. (2) Processes and procedures are being developed to populate xref2 for SAP generated transactions.  The information will be shared with [NAME].
#16-Cash Forecash Report ([NAME])  (Needed 7/5) | ZCASH | Accounting\Enron Enhancements\Accounts Payable\Cash Management\Cash Flow\Accounts Payable\By Expected Date | Report breakdown by commodity type | (1) Report needs to be sorted by xref2 below the company code level sort.  (2) Xref2 field needs to be populated for data converted from MSA | [NAME], zcash programmer,  said the changes requested in the spec are simple changes that don't require a great deal of time. No changes can occur in zcash before 7/1, but changes can be made after 7/1 to be available on 7/7.    This change has been requested by financial and treasury also. | R:  [NAME] and [NAME] met to review the new, detailed tech spec that requests forecasting information to be sorted by xref2.  (2) xref2 field will be populated for MSA data and SAP generated documents (see aging report for more details)  AI: (1) Maura to make small modifications in the spec and send to Kris for review, who will forward  to [NAME] and [NAME] for approval. (2) Kris to observe MSA data interface results (3) Rainier to find out how soon the changes can be implemented after 7/1
#17-Forecasted Invoices by Expected Date  (Needed 7/5) | ZCASH | Accounting\Enron Enhancements\Accounts Payable\Cash Management\Accounts Payable\Cash Flow\Accounts Payable\By Expected Date | Report breakdown by commodity type | (1) Report needs to be sorted by xref2 below the company code level sort.  (2) Xref2 field needs to be populated for data converted from MSA | [NAME], zcash programmer,  said the changes requested in the spec are simple changes that don't require a great deal of time. No changes can occur in zcash before 7/1, but changes can be made after 7/1 to be available on 7/7.    This change has been requested by financial and treasury also. | R:  [NAME] and [NAME] met to review the new, detailed tech spec that requests forecasting information to be sorted by xref2.  (2) xref2 field will be populated for MSA data and SAP generated documents (see aging report for more details)  AI: (1) Maura to make small modifications in the spec and send to Kris for review, who will forward  to [NAME] and [NAME] for approval. (2) Kris to observe MSA data interface results (3) Rainier to find out how soon the changes can be implemented after 7/1