Marketrak phase 2b
This presentation is the property of its rightful owner.
Sponsored Links
1 / 38

MarkeTrak Phase 2b PowerPoint PPT Presentation


  • 77 Views
  • Uploaded on
  • Presentation posted in: General

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.

Download Presentation

MarkeTrak Phase 2b

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Marketrak phase 2b

MarkeTrak Phase 2b

Technical Walk Through


Req 5 add parent issue number

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


Req 5 add parent issue number1

Req 5 – Add Parent Issue Number


Req 5 add parent issue number2

Req 5 – Add Parent Issue Number

  • API

    • Added “ParentIssueNumber” element to “QueryResponseIssueType” complex type

    • Added new element “ParentIssueNumber” string length 16.


Req 5 add parent issue number3

Req 5 – Add Parent Issue Number

  • Bulk

    • No changes


Req 9 comments required on siebel chg info

Req 9 – Comments Required on Siebel Chg/Info

  • GUI

    • Comments now required on Submit of new D2D-Siebel Chg/Info Issues


Req 9 comments required on siebel chg info1

Req 9 – Comments Required on Siebel Chg/Info


Req 9 comments required on siebel chg info2

Req 9 – Comments Required on Siebel Chg/Info

  • API

    • Large structural change

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


Req 9 comments required on siebel chg info3

Req 9 – Comments Required on Siebel Chg/Info

  • Bulk

    • Comments now required on Submit of new D2D-Siebel Chg/Info Issues


Req 9 comments required on siebel chg info4

Req 9 – Comments Required on Siebel Chg/Info


Req 10 add service period start stop to d2d subtypes

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

  • GUI

    • Service Period Start Date optional on:

      • Missing Transaction

      • Projects

      • Siebel Chg/Info

      • Other

    • Service Period Start Date required on:

      • Rep of Record

      • Usage and Billing

    • Service Period Stop Date optional on:

      • Rep of Record

      • Usage and Billing


Req 10 add service period start stop to d2d subtypes1

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


Req 10 add service period start stop to d2d subtypes2

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


Req 10 add service period start stop to d2d subtypes3

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

  • API

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

    • Add optional “StartTime” element to “MissingTrxnRespType”, “ProjRespType”, “SiebelRespType”, “OtherRespType”, “UsageBillingRespType” and “RepRecordRespType” complex types

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

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

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


Req 10 add service period start stop to d2d subtypes4

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

  • Bulk

    • New columns “Start Time” and “Stop Time” added to D2D table

    • “Start Time” marked optional for “Missing Txns”, “Projects”, “Siebel Chg/Info” and “Other” rows

    • “Start Time” marked required on “Usage/Billing Issues” and “Rep of Record” rows

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

    • All other rows not mentioned above had “Start Time” and “Stop Time” columns marked “N/A”


Req 10 add service period start stop to d2d subtypes5

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


Req 11 add isa field to d2d subtypes

Req 11 – Add ISA Field to D2D subtypes

  • GUI

    • ISA Number field optional on:

      • Projects

      • Other

    • ISA Number field required on:

      • 997 Issues


Req 11 add isa field to d2d subtypes1

Req 11 – Add ISA Field to D2D subtypes


Req 11 add isa field to d2d subtypes2

Req 11 – Add ISA Field to D2D subtypes


Req 11 add isa field to d2d subtypes3

Req 11 – Add ISA Field to D2D subtypes

  • API

    • Add optional “ISANum” element to “ProjType”, “OtherType”, “ProjRespType”, “D2d997RespType” and “OtherRespType” complex types

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

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


Req 11 add isa field to d2d subtypes4

Req 11 – Add ISA Field to D2D subtypes

  • Bulk

    • New column “ISA Number” added to D2D table

    • “ISA Number” marked optional for “Projects” and “Other” rows

    • “ISA Number” marked required on “997 Issues” row

    • All other rows not mentioned above had “ISA Number” column marked “N/A”


Req 11 add isa field to d2d subtypes5

Req 11 – Add ISA Field to D2D subtypes


Req 12 reject txns sub type changes

Req 12 – Reject Txns sub-type Changes

  • GUI

    • Reject Code required on submits

    • Reject Code drop down list of valid Texas Set Reject codes based on selected Tran Type

    • Comments required if Reject Code “A13” selected

    • Reduce Tran Type drop down selections to: 814_02, 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_27, 814_29, 824


Req 12 reject txns sub type changes1

Req 12 – Reject Txns sub-type Changes


Req 12 reject txns sub type changes2

Req 12 – Reject Txns sub-type Changes


Req 12 reject txns sub type changes3

Req 12 – Reject Txns sub-type Changes


Req 12 reject txns sub type changes4

Req 12 – Reject Txns sub-type Changes

  • API

    • Modify “RejectTrxnType” complex type to use “TrxnRejectType” element instead of “TrxnType”

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

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


Req 12 reject txns sub type changes5

Req 12 – Reject Txns sub-type Changes

  • Bulk

    • New column “Reject Code” added to D2D table

    • “Reject Code” marked required for “Reject TXNs” row

    • All other rows not mentioned above had “Reject Code” column marked “N/A”


Req 12 reject txns sub type changes6

Req 12 – Reject Txns sub-type Changes


Req 20 capture date of 1 st begin working

Req 20 – Capture Date of 1st Begin Working

  • GUI

    • Add new field “First Touched” to contain the date of the Issue’s first “Begin Working” transition

    • “First Touched” field available for reporting

    • Move “Issue Available Date” field from system section to Info section for GUI User viewing

    • Both fields are read only and captured automatically by the application


Req 20 capture date of 1 st begin working1

Req 20 – Capture Date of 1st Begin Working


Req 20 capture date of 1 st begin working2

Req 20 – Capture Date of 1st Begin Working

  • API

    • Add optional “FirstTouched” element to “QueryResponseIssueType”

    • Define “FirstTouched” as a Date type


Req 20 capture date of 1 st begin working3

Req 20 – Capture Date of 1st Begin Working

  • Bulk

    • No Changes


Req 30 new total to dev idr sub types

Req 30 – New Total to DEV IDR sub-types

  • GUI

    • Add requied “New Total” field to DEV IDR sub-types:

      • In MP system, but not in ERCOT system

      • In both systems, but with date issues

      • In both systems, but with kwh issues


Req 30 new total to dev idr sub types1

Req 30 – New Total to DEV IDR sub-types


Req 30 new total to dev idr sub types2

Req 30 – New Total to DEV IDR sub-types

  • API

    • Add required “New Total” element to "IDRUsageMPNotErcotType“, "IDRUsageDateType”, and "IDRUsagekWhType“ complex types


Req 30 new total to dev idr sub types3

Req 30 – New Total to DEV IDR sub-types

  • Bulk

    • Add a new column “New Total”

    • Mark all rows required

    • Mark “In ERCOT system not MP” rows as “N/A”


Req 34 support xml special characters

Req 34 – Support XML Special Characters

  • Deferred till December release (release 3)


  • Login