Clear Cutover Get a quote

For Epicor partners, on Kinetic

The report and BAQ tickets every client keeps sending. Off your consultants' plates.

"Add one field to the pack slip." "The invoice broke after the upgrade." "This BAQ shows every order twice." I take these as fixed-fee subcontract tickets, work from the files you send, and hand back finished work under your name.

Send me one ticket to price See which tickets I take

SQL Server and SSRS background from three years in-house on an ERP system at a Sydney manufacturer. Working your business hours in Australia, the UK, Europe, the US and Canada.

Example partner queue 6 open
  1. RDLPackSlip: add customer part numberOPEN
  2. RDLOrder ack: add a UD field from the order headerOPEN
  3. FIXAR invoice: "invalid column name" after upgradeOPEN
  4. BAQOpen orders: totals doubled on multi-release linesOPEN
  5. BAQFill rate shows 0%OPEN
  6. DMTCustomer and order batch: pre-load checkOPEN
Fixed fee, written notes with every ticketIllustrative example, not client data
Fixed fee, agreed first

Every ticket is priced before I start. If the first of a type takes me longer, that's my cost, not your client's.

Your files, your name

I work from downloaded files by default, in your Pilot when a ticket needs it, never in production.

Clear limits

I list exactly what I take. If a ticket is outside it, I say so before quoting.

Five ticket types, each with a clear finish line

The first three are the weekly tickets every partner queue is full of. The last two come up around upgrades, cloud moves and data migrations.

Weekly tickets Fixed per ticket

Most requested

SSRS report field and layout adds

New fields, columns and layout changes on standard forms such as the pack slip, order acknowledgment and AR invoice.

What's included
  • Excluded columns un-excluded on a copy of the standard RDD, and linked tables added when the field lives elsewhere
  • The RDL dataset query and field list edited by hand, never rebuilt with Sync Dataset
  • Work done on a copy of the standard report style, never the system style
  • Rendered against staged report data before handover
  • On cloud: the names from the downloaded zip kept, and the file re-downloaded after upload to confirm the change is there

Fixed per ticket. RDD changes listed so your consultant can apply them, or applied in your Pilot.Typical prices

Every upgrade

Post-upgrade report fixes

For custom reports that stopped working after a version change.

What's included
  • "Invalid column name" errors traced to columns the upgraded RDD no longer has
  • Styles copied from the wrong base report, such as an AR form built on a different RDD than the client's base style uses
  • Reports damaged by Sync Dataset, with the dataset query restored by hand
  • Upload failures caused by a Report Location that doesn't match the file, or a re-saved file's format version
  • A written note of the cause, so the same break doesn't come back next upgrade

Fixed per report. Often bundled with field adds on the same report.Typical prices

Weekly

BAQ fixes

For BAQs that return duplicated rows, wrong totals, missing records or run slowly.

What's included
  • Missing Company joins that let another company's records in
  • CustID joined to CustNum, causing conversion errors or silent wrong matches
  • Release joins multiplying order lines and inflating totals
  • Criteria sitting on a subquery that doesn't limit the output
  • The wrong date field driving "late" or "overdue" logic
  • Integer division showing percentages as 0
  • Slow BAQs reviewed with the query execution plan

You get a corrected BAQ and a written diagnosis your consultant can forward. Fixed per BAQ.Typical prices

Weekly

New BAQs and BAQ Reports

Straightforward list queries and the printable BAQ Reports built on them.

What's included
  • Joins, left joins, subqueries and calculated fields
  • Grouped BAQ Reports with subtotals, for example open orders by customer with days late
  • The cloud-safe route for reports that used to read the database directly

Fixed per BAQ or report. Updatable BAQs and dashboards are not included.Typical prices

Upgrade, cloud and migration projects Fixed fee

Before a cloud move

Report backlog triage

A five-day, read-only, fixed-fee audit of a client's custom reports before an upgrade or cloud cutover.

What's included
  • Every custom report style, RDD, BAQ and BAQ Report put into one inventory, with owner, last run and run count
  • Each one checked for what blocks it on cloud: its own SQL data source, a stored-procedure dataset, SQL views, file writes, or MES printing needs
  • BAQs scanned for the known defects above, and multi-company totals compared
  • A verdict per report: Keep, Rebuild as BAQ Report, Replace with a grid, or Retire
  • A summary, the top risks and a fixed-scope quote for the follow-on work

Needs a read-only Kinetic user. Nothing is changed during the audit.Typical prices

Before a load

DMT pre-load validation

Catch the problems that fail a DMT load before anyone runs it.

What's included
  • Covers Customer, ShipTo, Part, PartPlant, Sales Order header and Sales Order lines
  • Required columns, data types, dates, duplicate keys, and parents missing from the batch, always within the same Company
  • Hidden spaces and characters, unknown UOMs, sites and warehouses
  • Load order checked: customers before ship-tos and orders, parts before plants and order lines
  • A remediation report listing every finding by file, row and check, with its basis
  • Built on my own validator, which found all 15 of 15 planted errors in a lab test batch

You send the CSVs, plus an export of existing records for Update loads. No tenant access needed.Typical prices

What I don't take

Crystal-to-SSRS conversions, dashboards and Application Studio layers, BPM directives, Epicor Functions, System Agent schedules, and integrations (REST, Service Connect, EDI). If a ticket needs any of these, I'll tell you before quoting rather than learn on your client's time.

What you send, what you get back

Most tickets need no access to your client's system at all.

What to send and what you get back for each ticket type
TicketYou sendYou get backAccess
Field and layout addsThe downloaded report bundle and the list of fieldsThe edited RDL, tested against staged data, and any RDD changes listedNone, or Pilot if the RDD changes
Post-upgrade fixesThe report bundle, the error message and the releaseThe fixed RDL and a note of the causeNone, or Pilot to reproduce
BAQ fixes and new BAQsA BAQ export or a Pilot login, and what's wrongThe corrected BAQ and a written diagnosisPilot only
Report backlog triageReport style, BAQ and RDD lists, and report ownersThe inventory, a verdict per report, top risks and a quoteRead-only user
DMT pre-load validationThe CSVs and, for Update loads, an export of existing recordsThe remediation report and load-order checkNone

How a subcontract ticket runs

  1. Send one ticket

    Start with one to see the work. Include the client's Kinetic release and whether it's cloud or on-premise.

  2. Fixed quote

    A price and turnaround in writing before I start, under your NDA and subcontract terms.

  3. Check, then build

    I confirm behavior against the client's release first, then work from files or in your Pilot.

  4. Hand back

    Finished files, notes your consultant can use with the client, and anything I noticed outside the ticket.

White-label by default. I work in your tooling and ticket system, report to your lead, and never contact your client unless you ask me to.

Moving a client off SyteLine?

I know the source system too

I spent three years in-house on Infor SyteLine at a Sydney manufacturer, including the data workstream of a full cutover to another ERP. Items, BOMs, customers, suppliers and orders were extracted, cleansed, mapped and validated, and manufacturing and order fulfilment kept running through go-live.

  • Data extracted and cleansed from SyteLine's SQL Server database, read-only, on a copy
  • SyteLine sites mapped to Kinetic companies and plants before the first load
  • SyteLine customer numbers carried into Kinetic as CustIDs, never as CustNums
  • Each converted batch checked with the DMT validator before every load cycle

Where my Kinetic experience comes from

My production experience is SQL Server, SSRS and ERP data on Infor SyteLine. My Kinetic skills come from a structured lab on SQL Server 2016 and SSRS 2016: a two-company test database, report labs on the pack slip, order acknowledgment and AR form, graded BAQ build and fix drills, a DMT validator, and a timed five-ticket readiness exam, which I passed. Every demo I show you is labelled as a lab exercise.

What that means for you

  • I take only the ticket types above, and say so before quoting if something is outside them
  • The first ticket of each type is a fixed fee, so any extra time is mine
  • I check behavior against your client's Kinetic release before touching anything
  • Short demos of a DMT check, a pack slip change and a BAQ fix are available on request

Epicor Kinetic guides

Free, practical write-ups on the same ticket types I take. See all Kinetic guides.

Send me one ticket to price

Include the ticket type and the files (or a description if files can't leave yet), the client's Kinetic release, cloud or on-premise, and your deadline and time zone. I'll quote within one business day.

Send a ticket

Systems I work on