Top Banner
MarkeTrak Phase 2b MarkeTrak Phase 2b Technical Walk Through Technical Walk Through
38

MarkeTrak Phase 2b

Jan 01, 2016

Download

Documents

MarkeTrak Phase 2b. Technical Walk Through. Req 5 – Add Parent Issue Number. GUI New field to contain the Parent Issue Number Used with Bulk Insert “child” Issues to identify the Bulk Insert “Parent” Issue Number Automatically populated by Bulk Insert process. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: MarkeTrak Phase 2b

MarkeTrak Phase 2bMarkeTrak Phase 2b

Technical Walk ThroughTechnical Walk Through

Page 2: MarkeTrak Phase 2b

Req 5 – Add Parent Issue NumberReq 5 – Add Parent Issue Number

GUIGUI New field to contain the Parent Issue NumberNew field to contain the Parent Issue Number Used with Bulk Insert “child” Issues to identify Used with Bulk Insert “child” Issues to identify

the Bulk Insert “Parent” Issue Numberthe Bulk Insert “Parent” Issue Number Automatically populated by Bulk Insert Automatically populated by Bulk Insert

processprocess

Page 3: MarkeTrak Phase 2b

Req 5 – Add Parent Issue NumberReq 5 – Add Parent Issue Number

Page 4: MarkeTrak Phase 2b

Req 5 – Add Parent Issue NumberReq 5 – Add Parent Issue Number

APIAPI Added “ParentIssueNumber” element to Added “ParentIssueNumber” element to

“QueryResponseIssueType” complex type“QueryResponseIssueType” complex type Added new element “ParentIssueNumber” Added new element “ParentIssueNumber”

string length 16.string length 16.

Page 5: MarkeTrak Phase 2b

Req 5 – Add Parent Issue NumberReq 5 – Add Parent Issue Number

BulkBulk No changesNo changes

Page 6: MarkeTrak Phase 2b

Req 9 – Comments Required on Req 9 – Comments Required on Siebel Chg/InfoSiebel Chg/Info

GUIGUI Comments now required on Submit of new Comments now required on Submit of new

D2D-Siebel Chg/Info IssuesD2D-Siebel Chg/Info Issues

Page 7: MarkeTrak Phase 2b

Req 9 – Comments Required on Req 9 – Comments Required on Siebel Chg/InfoSiebel Chg/Info

Page 8: MarkeTrak Phase 2b

Req 9 – Comments Required on Req 9 – Comments Required on Siebel Chg/InfoSiebel Chg/Info

APIAPI Large structural changeLarge structural change Removed “CommentText” element from Removed “CommentText” element from

IssueSubmitRequest complex element and IssueSubmitRequest complex element and added to “Issue{subtype}type” complex added to “Issue{subtype}type” complex elements and created elements and created ‘Issue{subtype}Resptype” complex elements‘Issue{subtype}Resptype” complex elements

Page 9: MarkeTrak Phase 2b

Req 9 – Comments Required on Req 9 – Comments Required on Siebel Chg/InfoSiebel Chg/Info

BulkBulk Comments now required on Submit of new Comments now required on Submit of new

D2D-Siebel Chg/Info IssuesD2D-Siebel Chg/Info Issues

Page 10: MarkeTrak Phase 2b

Req 9 – Comments Required on Req 9 – Comments Required on Siebel Chg/InfoSiebel Chg/Info

Page 11: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

GUIGUI Service Period Start Date optional on:Service Period Start Date optional on:

Missing TransactionMissing TransactionProjectsProjectsSiebel Chg/InfoSiebel Chg/InfoOther Other

Service Period Start Date required on:Service Period Start Date required on:Rep of RecordRep of RecordUsage and Billing Usage and Billing

Service Period Stop Date optional on:Service Period Stop Date optional on:Rep of RecordRep of RecordUsage and BillingUsage and Billing

Page 12: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

Page 13: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

Page 14: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

APIAPI Add optional “StartTime” element to “MissingTrxnType”, Add optional “StartTime” element to “MissingTrxnType”,

“ProjType”, “SiebelType” and “OtherType” complex types“ProjType”, “SiebelType” and “OtherType” complex types Add optional “StartTime” element to “MissingTrxnRespType”, Add optional “StartTime” element to “MissingTrxnRespType”,

“ProjRespType”, “SiebelRespType”, “OtherRespType”, “ProjRespType”, “SiebelRespType”, “OtherRespType”, “UsageBillingRespType” and “RepRecordRespType” complex “UsageBillingRespType” and “RepRecordRespType” complex typestypes

Add required “StartTime” element to “UsageBillingType” and Add required “StartTime” element to “UsageBillingType” and “RepRecordType” complex types“RepRecordType” complex types

Add optional “StopTime” element to “UsageBillingType” and Add optional “StopTime” element to “UsageBillingType” and “RepRecordType “ complex types“RepRecordType “ complex types

Add optional “StopTime” element to “UsageBillingRespType” Add optional “StopTime” element to “UsageBillingRespType” and “RepRecordRespType” complex typesand “RepRecordRespType” complex types

Page 15: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

BulkBulk New columns “Start Time” and “Stop Time” added to New columns “Start Time” and “Stop Time” added to

D2D tableD2D table ““Start Time” marked optional for “Missing Txns”, Start Time” marked optional for “Missing Txns”,

“Projects”, “Siebel Chg/Info” and “Other” rows“Projects”, “Siebel Chg/Info” and “Other” rows ““Start Time” marked required on “Usage/Billing Start Time” marked required on “Usage/Billing

Issues” and “Rep of Record” rowsIssues” and “Rep of Record” rows ““Stop Time” marked optional on “Usage/Billing Issues” Stop Time” marked optional on “Usage/Billing Issues”

and “Rep of Record“ rowsand “Rep of Record“ rows All other rows not mentioned above had “Start Time” All other rows not mentioned above had “Start Time”

and “Stop Time” columns marked “N/A”and “Stop Time” columns marked “N/A”

Page 16: MarkeTrak Phase 2b

Req 10 – Add Service Period Req 10 – Add Service Period Start/Stop to D2D subtypesStart/Stop to D2D subtypes

Page 17: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

GUIGUI ISA Number field optional on:ISA Number field optional on:

ProjectsProjects

Other Other ISA Number field required on:ISA Number field required on:

997 Issues997 Issues

Page 18: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

Page 19: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

Page 20: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

APIAPI Add optional “ISANum” element to “ProjType”, Add optional “ISANum” element to “ProjType”,

“OtherType”, “ProjRespType”, “OtherType”, “ProjRespType”, “D2d997RespType” and “OtherRespType” “D2d997RespType” and “OtherRespType” complex typescomplex types

Add required “ISANum” element to Add required “ISANum” element to “D2d997Type” complex type“D2d997Type” complex type

Define an “ISANumDef” element as string 9 Define an “ISANumDef” element as string 9 character maxcharacter max

Page 21: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

BulkBulk New column “ISA Number” added to D2D New column “ISA Number” added to D2D

tabletable ““ISA Number” marked optional for “Projects” ISA Number” marked optional for “Projects”

and “Other” rowsand “Other” rows ““ISA Number” marked required on “997 ISA Number” marked required on “997

Issues” rowIssues” row All other rows not mentioned above had “ISA All other rows not mentioned above had “ISA

Number” column marked “N/A”Number” column marked “N/A”

Page 22: MarkeTrak Phase 2b

Req 11 – Add ISA Field to D2D Req 11 – Add ISA Field to D2D subtypessubtypes

Page 23: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

GUIGUI Reject Code required on submits Reject Code required on submits Reject Code drop down list of valid Texas Set Reject Reject Code drop down list of valid Texas Set Reject

codes based on selected Tran Typecodes based on selected Tran Type Comments required if Reject Code “A13” selectedComments required if Reject Code “A13” selected Reduce Tran Type drop down selections to: 814_02, Reduce Tran Type drop down selections to: 814_02,

814_04, 814_05, 814_07, 814_09, 814_11, 814_13, 814_04, 814_05, 814_07, 814_09, 814_11, 814_13, 814_15, 814_17, 814_19, 814_21, 814_23, 814_25, 814_15, 814_17, 814_19, 814_21, 814_23, 814_25, 814_27, 814_29, 824 814_27, 814_29, 824

Page 24: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

Page 25: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

Page 26: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

Page 27: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

APIAPI Modify “RejectTrxnType” complex type to use Modify “RejectTrxnType” complex type to use

“TrxnRejectType” element instead of “TrxnRejectType” element instead of “TrxnType”“TrxnType”

Add required “RejectCode” element to Add required “RejectCode” element to “RejectTrxnType” complex type“RejectTrxnType” complex type

Define “TrxnRejectType” and “RejectCode” Define “TrxnRejectType” and “RejectCode” elements with enumerationselements with enumerations

Page 28: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

BulkBulk New column “Reject Code” added to D2D New column “Reject Code” added to D2D

tabletable ““Reject Code” marked required for “Reject Reject Code” marked required for “Reject

TXNs” rowTXNs” row All other rows not mentioned above had All other rows not mentioned above had

“Reject Code” column marked “N/A”“Reject Code” column marked “N/A”

Page 29: MarkeTrak Phase 2b

Req 12 – Reject Txns sub-type Req 12 – Reject Txns sub-type ChangesChanges

Page 30: MarkeTrak Phase 2b

Req 20 – Capture Date of 1Req 20 – Capture Date of 1stst Begin Begin WorkingWorking

GUIGUI Add new field “First Touched” to contain the Add new field “First Touched” to contain the

date of the Issue’s first “Begin Working” date of the Issue’s first “Begin Working” transition transition

““First Touched” field available for reportingFirst Touched” field available for reporting Move “Issue Available Date” field from system Move “Issue Available Date” field from system

section to Info section for GUI User viewingsection to Info section for GUI User viewing Both fields are read only and captured Both fields are read only and captured

automatically by the application automatically by the application

Page 31: MarkeTrak Phase 2b

Req 20 – Capture Date of 1Req 20 – Capture Date of 1stst Begin Begin WorkingWorking

Page 32: MarkeTrak Phase 2b

Req 20 – Capture Date of 1Req 20 – Capture Date of 1stst Begin Begin WorkingWorking

APIAPI Add optional “FirstTouched” element to Add optional “FirstTouched” element to

“QueryResponseIssueType”“QueryResponseIssueType” Define “FirstTouched” as a Date typeDefine “FirstTouched” as a Date type

Page 33: MarkeTrak Phase 2b

Req 20 – Capture Date of 1Req 20 – Capture Date of 1stst Begin Begin WorkingWorking

BulkBulk No ChangesNo Changes

Page 34: MarkeTrak Phase 2b

Req 30 – New Total to DEV IDR Req 30 – New Total to DEV IDR sub-typessub-types

GUIGUI Add requied “New Total” field to DEV IDR Add requied “New Total” field to DEV IDR

sub-types:sub-types:In MP system, but not in ERCOT systemIn MP system, but not in ERCOT system

In both systems, but with date issuesIn both systems, but with date issues

In both systems, but with kwh issues In both systems, but with kwh issues

Page 35: MarkeTrak Phase 2b

Req 30 – New Total to DEV IDR Req 30 – New Total to DEV IDR sub-typessub-types

Page 36: MarkeTrak Phase 2b

Req 30 – New Total to DEV IDR Req 30 – New Total to DEV IDR sub-typessub-types

APIAPI Add required “New Total” element to Add required “New Total” element to

"IDRUsageMPNotErcotType“, "IDRUsageMPNotErcotType“, "IDRUsageDateType”, and "IDRUsageDateType”, and "IDRUsagekWhType“ complex types"IDRUsagekWhType“ complex types

Page 37: MarkeTrak Phase 2b

Req 30 – New Total to DEV IDR Req 30 – New Total to DEV IDR sub-typessub-types

BulkBulk Add a new column “New Total”Add a new column “New Total” Mark all rows requiredMark all rows required Mark “In ERCOT system not MP” rows as Mark “In ERCOT system not MP” rows as

“N/A”“N/A”

Page 38: MarkeTrak Phase 2b

Req 34 – Support XML Special Req 34 – Support XML Special CharactersCharacters

Deferred till December release (release 3)Deferred till December release (release 3)