EMAIL CCR1-ExportImport Data - SR588 CCR1 - DBRD CCR1 Proposed Design Overview

From: Milton, Bridget
Sent: Friday, May 03, 2013 12:35 AM
To: Beamish, Paul
Subject: FW: SR588/CCR1 - DBRD, CCR1, Proposed Design Overview, Analysis
Importance: High
Finally!
This email was provided to Ashish as an effort to catch him up to date on SR588/CCR1. In addition to the
DBRD, CCR1, etc, below I’ve included a Proposed Design Overview which indicates the areas that require
additional analysis, etc. The highlighted items of the proposed overview are what I believe are questions that
should be asked of GNG. I don’t anticipate you sending this email to GNG, so let me know if/when you
need me to place the questions for GNG into a separate mail.
Lastly, the information provided in the Proposed Design Overview section is essentially what I’m using to
write the HLD, again, there’s still quite a bit of analysis needed to confirm the proposed design. I will have a
better idea of when the HLD will be ready for an internal review once I have Ashish up to speed and he can
share insight or assist with analysis on the solution. In the interim, the information about the design should
provide a decent amount of insight on the proposed design.
Let me know if there are questions/concerns.
Sent: Friday, May 03, 2013 12:22 AM
To: Goel, Ashish
Cc: Wilson, Rodney
Subject: SR588/CCR1 - DBRD, CCR1, Proposed Design Overview, Analysis
Importance: High
Ashish,
I understand you will be working with me on SR588-Auto Upload Service Locations into Banner. SR 588/CCR1 will
establish Units for newly created agreements manually created via uzaacna by the A.C.N team. Please find the latest
DBRDv1.8 and CCR1v1.2. These docs are in the final phase of being approved by GNG.
There has been quite a bit of analysis along with work done on the HLD for this project. Below provides an outline of
the proposed design overview. As stated in the overview, there are areas that still require analysis and input from
GNG. The highlighted sections require input from GNG to confirm the design.
Please let me know when you’ve had a chance to read through the provided material and we can set up a time to walk
through the SR to date and ensure we’re consistent with the SR’s expectations. Feel free to ask questions at any
point. I can be best reached via email, however, please feel free to call 972.529.2224 / 214.869.0276.
SR588/CCR1 – Proposed Design Overview
1. A new Banner process is run to pick up the FTP’d World CD type file and store on a Banner read-only table, name
TBD. See attached spreadsheet, SR588 Summary gtbacna-gtracnu-World CD data mapping, tab-World CD-Rent Roll
for an example of the World Cd we’re to received from GNG
a. There is an assumption that the monthly World CD file received from GNG will only be overwritten
by the receipt of another World CD file from GNG. GNG to confirm if they have a preference on

whether the monthly World CD file should be overwritten by data value changes completed by the
A.C.N team.
b. The process to pick up the file is to be determined, there has been discussion to determine if the
process, uzppucp, can be used to upload the World CD file. There is an understanding that uzppucp
is used to upload an annual World CD file and store onto the uzbagld table.
c. The directory the World CD will be stored is still being determined.
2. In addition to storing the World CD data into a Banner directory and onto a to be determined new table, a second
copy of the World CD data will be stored into a data source.
a. The type of data source is yet to be determined; however, the following are some suggestions that
require additional analysis:
i. Excel Spreadsheet: Store the World CD data into an excel spreadsheet if
there is a way to provide the A.C.N team the ability to query 3-4 field variables.
ii. Banner-Online A.C.N Reporting Run Using Main Menu: There’s
been discussion to use the logic used to run existing A.C.N Report Options that are run
online in Banner using the Menu options. The logic should provide the A.C.N team the
ability to query 3-4 field variables of the World CD report. See attached spreadsheet,
“Your Thoughts SR588-CCR1 Data Source”. This attachment has embedded
documents and email content that shares analysis performed to confirm whether the
data source to store World CD data that will be queried by the A.C.N team can be
Banner and if the logic used to generate the online A.C.N reports via Banner’s Main
Menu options. A final decision was not determined.
b. The A.C.N New Unit Data file will include two fields the A.C.N team will provide values needed to
establish units that will be systematically associated the newly created agreements. The two fields are
AGLC Agreement # and Status.
3. The World CD data will be loaded into the confirmed data source.
4. The A.C.N team will have the ability to query 3-4 field variables in the chosen data source to generate an initial
account list that will ultimately be used to create new agreements and its units.
a. GNG to provide the fields and their values that should be captured from the World CD and
ultimately used to create the A.C.N New Unit Data file
b. GNG to provide all of the fields that can be queried by the A.C.N team, understanding an executed
query will be based on up to 3-4 field variables.
c. GNG to confirm if there should be a maximum number of rows/columns returned with queries
executed against the World CD file.
5. Once the World CD has been queried the data is exported into a spreadsheet. The exported spreadsheet of the
World CD data is now known as the A.C.N New Unit Data file.
6. The A.C.N New Unit Data file will be verified for accuracy against the Rent-Roll report.
a. GNG to provide additional specifics/steps the A.C.N team should follow to verify the A.C.N New
Unit Data file to the Rent-Roll Report
7. Once the A.C.N New Unit Data file has been corrected, the A.C.N team member will use the file’s content to create
agreements manually via Banner form, uzaacna.
8. The A.C.N New Unit Data file will include two fields that will require the A.C.N team members to enter values in the
fields for each row, field names AGLC Agreement # and Status. The field’s values are necessary to systematically
associate newly created agreements to units that are to be systematically established via SR588/CCR1.
9. The AGLC Agreement # and Status fields in the A.C.N New Unit Data file will be NULL until the A.C.N team
member enters the correct value.
a. The AGLC Agreement # and Status fields definitions and expected values are as follows:
i. AGLC Agreement #: This field will include the AGLC Agreement Number
the A.C.N team member obtained via email from AGLC. See attached spreadsheet, “SR588
Summary gtbacna-gtracnu-World CD data mapping, tab-New Contract Email” for an example
of the email communication between AGLC and the A.C.N team to obtain the Agreement #.
ii. Status-Ready for Processing: Once the A.C.N team member has
corrected the data on the A.C.N New Unit Data file and created the agreement using the data

values. The A.C.N team member will enter a value of “Ready for Processing” in the Status
field.
10. Once the A.C.N New Unit Data file has been verified for accuracy, the agreements have been created manually
using the UZAACNA A.C.N Maintenance form and the AGLC Agreement # and The Status field values have been
entered where appropriate. The file will be uploaded into Banner onto a new table.
a. The process or method used to upload the A.C.N New Unit Data file has not been determined,
however, there has been discussion that UZPCIRA may contain similar logic needed to upload the file.
b. The process or method used to upload the A.C.N New Unit Data file will not have data verification,
all of the file’s content will be allowed to be loaded into Banner. See step 14 for additional information
on Exception Handling.
11. In addition to loading the file content from the A.C.N New Unit Data file, the new process, potentially uzpcira, will
systematically establish units for the newly created agreements. See attached spreadsheet, “SR588 Summary
gtbacna-gtracnu-World CD data mapping, tab-gtbacna_gtracnu_world_cd” for additional details on the mapping of the
field values between gtbacna, gtracnu and the World Cd file.
a. NOTE: When an agreement is created via uzaacna, the AGLC Agreement # (from AGLC) is
entered into the form and stored in the gtbacna_agreement_id field. Additionally, Banner auto-
generates a unique agreement id, gtbacna_agreement_nbr that is used to link the agreement to the
unit that will be systematically created, field gtracnu_agreement_nbr.
12. The new process, potentially uzpcira, will perform the following steps to systematically create units for the newly
created agreements:
a. The process will identify the AGLC Agreement # in the gtbacna_agreement_id field and select
from the gtbacna table the gtbacna_agreement_nbr, this value will be entered onto the units table,
gtracnu in the gtracnu_agreement_nbr field.
b. The process will identify the AGLC Agreement # on the new table created to store the A.C.N New
Unit Data and select the AGLC Prem ID and enter into the value onto the units table gtracnu, into the
GTRACNU_LDC_PREM_ID field.
i. NOTE: The HLD will provide additional specifics of the data mapping
necessary to systematically establish units.
13. Once the new process, potentially uzpcira, has completed, the process will update the status field on the new table
that contains the New A.C.N New Unit data. The statuses are as follows:
a. C=Complete: This status indicates the record successfully established its unit.
b. E=Exception: This status indicates the unit for this record was not created. See step ### for
additional information on Exception Reporting.
14. Records that were not used to create units will be reported on an Exception Report that will be produced by the
new process, potentially uzpcira. The following are some identified scenarios that will appear on the Exception
Report. The storage of the report will need to be defined. The intent is to provide the report to the A.C.N team to
confirm the exceptions and correct the agreements where needed.
a. GNG/Vertex to define the report layout
b. GNG/Vertex to define the scenarios that should be captured on the Exception Report
c. GNG/Vertex to define the report’s name
d. GNG/Vertex to confirm the new process, potentially uzpcira, is not expected to abort…any failures
are captured on the Exception Report.
15. Error processing uploading A.C.N new unit data
a. The specifics of the process, ie process name, parameters, output, etc, to upload the New A.C.N
Unit Data file is still being determined. There has been discussion that SR588/CCR1 can use logic or
the actual uzpcira process to upload the A.C.N New Unit Data file. This is still being confirmed.
b. GNG/Vertex will need to confirm if there are specific scenarios that can cause the process,
potentially uzpcira, to fail
c. The assumption is made that the process defined to upload the A.C.N New Unit Data file will abort
and include the reason for the abort on the .log and .lis reports.
i. If determined there are instances where the A.C.N New Unit Data file can
abort, the .lis and .log file layout and content will need to be confirmed
d. If there is an example where the A.C.N team member did not enter the Agreement # and/or Status
on the New A.C.N Unit Data file for a row of data, once the process runs to establish units for the

agreement, the record will Exception and generate on the Exception Report mentioned in the DBRD.
From there the A.C.N team member will have the ability to manually create the Unit for its agreement.
16. Once the end-to-end processing of creating agreements and establishing units have been defined analysis can be
done to determine if/how SR588/CCR impacts the SLA.
Please consider the environment before printing this email.
The information contained in this e-mail and its attachments are confidential to the intended recipient and
may be legally privileged or otherwise protected from disclosure. If you have received this message in
error,you must not print this email or its attachments. Please notify the sender immediately and delete the
message and any attachments from your computer. The unauthorized use, disclosure, copying or alteration of
this message is forbidden. Emails are not secure and may contain viruses. Vertex accepts no responsibility
for viruses; it is your responsibility to scan or otherwise check this email and any attachments.
----- Forwarded Message -----
Naeem,
As part of SR588-CCR1 GNG asks that we upload the World CD type file into a data source which allows the A.C.N
team the ability to query the data using 3-4 field variables. I am working under the assumption we can copy some/all
of the design used today to generate A.C.N type reports via Banner menu options, see screen shots below along with
email trail. What are your thoughts, even if the solution is not using the suggested approach, I just need to know that
you’re ok with uploading the World CD data into a data source that will allow the A.C.N team the ability to query the
data. I am finalizing the DBRD & CCR1 and want to confirm there are not any areas we should explore since the
meeting that will impact the estimated hours for the SOW Design-Implmentation stage.
we had a walk, proon this after reviewing information Rodney shared on how the reporting is done. Please confirm
if you think it will have unintended impact to the already approved SOW D-I? Now is the time to look into the
estimated effort hours.
Bill/Alain,
For SR588-CCR1, GNG is requesting that we pick up a monthly World CD type file and store into a data source that
allows the A.C.N team the ability to query, CCR1 attached. In addition to the A.C.N team querying the World CD data,
they should have the ability to:
- Query
- Export (in excel format)
o Externally compare against the rent-roll
- Modify queried data
- Enter field values for two new fields
- Upload data
Rodney/Bill,
Please share any input on risks, impacts, etc that comes with uploading, querying, exporting, changing data,
uploading modified data into Banner. My guess is there will need to be a read/write/delete table privileges that
support querying, exporting, correcting, uploading modified data that overwrites original data.

From: Wilson, Rodney
Sent: Thursday, February 21, 2013 11:55 AM
To: Rehman, Naeem; Milton, Bridget
Subject: RE: SR 588-Auto load Vacant Tenant Locations into Banner *Revised Requirements*
It’s a temp table used by the report attached. I’ve also attached the procedure it uses to load this table.
From: Rehman, Naeem
To: Wilson, Rodney; Milton, Bridget
Thanks Rodney. I see “~” delimited columns in UZTACNL_RECORD. Here are a couple of records from GNGDBAN:
10955~JAC~JAMES R CLEMENTS ~JAMES R CLEMENTS ~770~889-
7518~~770~889-7518~~A~01-MAY-05~~~4910 HAMPTONS CLUB DRIVE~~~~~ALPHARETTA~GA~30004~~~4910
HAMPTONS CLUB DRIVE~~~~~ALPHARETTA~GA~30004
10624~JAC~JENNIFER MITCHLER~JENNIFER MITCHLER~999~999-9999~~000~~~A~01-MAY-05~~~2944 LEASA
COURT~~~~~MARIETTA~GA~30066~~2944~LEASA~CT~~~~MARIETTA~GA~30066
Can you please explain what are these values?
Thanks,
Naeem
From: Wilson, Rodney
Sent: February-20-13 4:20 PM
To: Milton, Bridget
Cc: Rehman, Naeem
Attached is the Oracle report. Let me know if this will suffice.
Sent: Wednesday, February 20, 2013 12:58 PM
To: Wilson, Rodney
Cc: Rehman, Naeem
Rodney,
Can you help assist with providing the logic used to create the A.C.N related reports that are done in Banner as
requested by a user. For SR588 where we’re creating units for newly created agreements. GNG has asked before we
upload the unit data to create units we should allow BO a chance to verify the data we receive from GNG against the
rent/roll report. My thoughts are we can use the same concept/design from reports that are already run by
demand. Once BO has verified the report and notified us, we have to either find a way to update based on their

feedback or asked that they update the file that we’re going to upload to create units. That still needs to be
determined.
In summary, Naeem would like to take a look at the logic used to create the A.C.N reports in Banner.
The screen shots are an example where I selected to run the A.C.N Listing Report.

972.529.2224 - office
214.869.0276 - cell
From: Rehman, Naeem
Sent: Wednesday, February 20, 2013 11:33 AM
To: Milton, Bridget
Bridget,
What report do they run today for unit data? Can you send me the code. Also, I haven’t seen the World CD
data and therefore don’t know what attributes/values can be used to create automatic data source and what should
be the input from the CRR. We also need to know what information/attributes will be on the rent-roll for
comparison. I’m also wondering if the AGL have the rent-roll, then why we shouldn’t use this information for creating
units? At least that would eliminate the verification step.
Thanks,
Naeem
Sent: February-20-13 12:02 PM
To: Rehman, Naeem
Subject: FW: SR 588-Auto load Vacant Tenant Locations into Banner *Revised Requirements*
Naeem,
I’m updating the DBRD and creating a CCR for the below updates from GNG. Can you share your insight on the
design of the items for the CCR, ie GNG’s request to now create a way that the a.cn team can query to find the unit
data. Today, they’re able to run a.cn reports via banner, my guess is we would replicate how that’s done…but if you
have an idea of what to do, let me know.
I will be sending the docs for you to review today…the docs are due to GNG/Paul today. Sorry for the late notice, I’ve
been slammed with another install these past few weeks.
Regards,
Bridget
972.529.2224 - office
214.869.0276 - cell
To: Rehman, Naeem
Subject: FW: SR 588-Auto load Vacant Tenant Locations into Banner *Revised Requirements*
fyi
Regards,

Bridget
972.529.2224 - office
214.869.0276 - cell
From: Stephen Carter [mailto:Stephen.Carter@southstarenergy.com]
To: Beamish, Paul; Heffron, Mark
Cc: Pappadakis, Steven; Michael Presto; Anne Webb; Wendy Ho; Nelly Mauta; Milton, Bridget
Subject: SR 588-Auto load Vacant Tenant Locations into Banner *Revised Requirements*
Paul,
Summary of changes:
GNG will send the AGL World CD data in a format to be agreed upon on a monthly basis.
Vertex to take the AGL World CD data and create a data source that can be queried by the CRR team.
Vertex will develop a query that has 3-4 fields variables that can be inputted to develop the initial account list.
Vertex CRR team to output the list and review the list against the Rent Roll and general data that will be supplied by
GNG.
GNG to supply guidance on how to create and work/verify the list vs. the rent-roll.
Vertex CRR team creates a final, update account list that will be used as the data to upload the list of accounts into
Banner.
Remaining requirements to stay the same.
Please see the below revised business requirements:
1. SR588.BR.1.20 updated to refer to the AGL World CD Data that will be sent to Vertex via FTP on a monthly
basis.
2. SR588.BR.1.30 monthly.
3. SR588.BR.1.40 this would be an internal report if still needed.
4. Remaining requirements should be unchanged.
Additional changes will be required to the system requirements to support the new process per above.
Let us know if you have any questions or feedback, thanks for working with us on this.
SC
Stephen Carter
Senior Vendor Analyst
404-685-4094 office
404-444-9065 mobile
stephen.carter@southstarenergy.com
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2238 / Virus Database: 2639/5586 - Release Date: 02/06/13

Bridget,
I see your point. How do they get the spreadsheet data today? I assumed that they’d have some
existing process that they’re comfortable with and don’t want us to make any changes. Please check with
Paul and Enrique to find the best process flow. I’m open in whichever way it is easier for them to
input/verify data.
Thanks,
Naeem
Sent: April-08-13 12:02 PM
To: Rehman, Naeem
Subject: RE: CCR1-Export/Import Data
Naeem,
I think these steps are great; however, the CCR1 requests:
1. upload World CD type data
2. create a data source to store the data that provides 3-4 field variables the A.C.N team can query against
(my initial thought is the data source would be Banner, but I suppose this can be a spreadsheet type query)
3. A.C.N queries data
4. A.C.N team exports queried data
5. A.C.N team review/verify data against rent-roll
6. A.C.N team corrects data
7. A.C.N team enters the field values needed to associate units to agreement
8. A.C.N team uploads (input) data back into Banner
9. SR588 identifies data based on status entered once data uploaded.
Please review the CCR and let me know your thoughts. During the call today, GNG did say in the World
CD data they may request all of the unit addresses for a specific street, however, they (A.C.N team) will have
to filter and only verify the units that are a part of an agreement. Stephen’s example was, a street name can
have 1500 units, however, only 1000 are for the agreement. Therefore, the A.C.N team should only review
the 1000 units.
Separate note: It seems that if SR588/CCR1 has the field values from the World CD and the Rent Roll that it
may be easier for us to do a compare update. Just a thought.
I may need to touch base with Enrique for his thoughts on this. But definitely get Paul’s input.
But I want us to be on the same page first. I’m ok with proposing the steps you’ve provided, I just want us to
both understand that the steps are different than what’s in CCR1???
Thanks.
From: Rehman, Naeem
Sent: Monday, April 08, 2013 11:24 AM
To: Milton, Bridget

Cc: Wilson, Rodney
Subject: RE: CCR1-Export/Import Data
OK. Here is what my understanding is after the conf. call:
1. A.C.N team would have the World CD data in the spreadsheet from the existing procedures
(They do it today…i.e. without SR588).
2. The A.C.N team will get the Agreement Number and Rent-Roll data (again this exists
today…The only change would be the time counted towards SLA)
3. The A.C.N team will associate the units with Agreement Number in the spreadsheet (This
would be a new column in the spreadsheet)
4. Once finished reviewing the data in the spreadsheet…and comparing it with the Rent-Roll,
the A.C.N team will export units data into CSV format. (This is a new step)
5. The SR588 process will use the CSV file (exported from the Excel sheet) as input
(instead of the world-cd data table) to parse/validate/load units data to the respective agreements
number in Banner.
6. Validation/processing for each unit has already been defined in the draft DBRD. Any
exceptions will be reported in the output file generated by SR588.
Please review and advise if you have any questions/comments/feedback.
Thanks,
Naeem
Sent: April-08-13 11:09 AM
To: Rehman, Naeem
Cc: Wilson, Rodney
Subject: CCR1-Export/Import Data
Naeem,
We have to think through how we will provide the A.C.N team ability to query World CD data, export data
into spreadsheet, allow team to upload verified/modified data from the spreadsheet/.csv doc
What I’m not sure of is how we can get the data uploaded back into BANNER…??
If you know, we can discuss, otherwise, we may have to discuss with Rodney.

EMAIL CCR1-ExportImport Data - SR588 CCR1 - DBRD CCR1 Proposed Design Overview

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (8)

Similar to EMAIL CCR1-ExportImport Data - SR588 CCR1 - DBRD CCR1 Proposed Design Overview

Similar to EMAIL CCR1-ExportImport Data - SR588 CCR1 - DBRD CCR1 Proposed Design Overview (20)

EMAIL CCR1-ExportImport Data - SR588 CCR1 - DBRD CCR1 Proposed Design Overview