ERP Analyzer health check reults

Opened the following case with support. I bet it gets solved here first…

After running the ERP Analyzer, the report shows a Health Check item with some cryptic info in it.

ID: Delete partdtl if not found on tforddtl where tfordline <> 0
Table: PartDtl
Description: Search partdtl based on Company using primary key where company is Company.company. Filter by tfordline <> 0. Search tforddtl for partdtl.company, partdtl.tfordnum, partdtl.tfordline and tforddtl.openline = true. If not found then partdtl.

That description is a little vague…

So I want to?

  1. find PartDtl records where PartDtl.tfordline <> 0
  2. find tforddtl records where tforddtl.company = partdtl.company
    AND tforddtl.tfordnum = partdtl.tfordnum
    AND tforddtl.tfordline = partdtl.tfordline
    AND and tforddtl.openline = true
  3. Any record found in 1, but not in 2, should be deleted from partdtl?

Especially confusing is “If not found then partdtl.”

Then what? Delete partdtl records?

Already requested the solution to the problem via the case. There are “checkers” and “fixers”, and via the case we’ll send you instructions on how to do both with a new data fix.

1 Like

Thanks.

I thought I would have to resolve them my self - BAQ’s or SQL queries to find " bad" records, and DMT to fix them.

Should I be asking support for a data fix for each one found? Do them all in one case, or in individual cases ( I have 4 more health check results - that aren’t as cryptic).

Support just needs the results of the “health checker”, and we’ll determine what, if any, data fixes need to be sent.

3 Likes

FWIW …

Below is the case page. Note that highlighted time is from over 2 hours ago, and not a single response beyond the automated message about the case being created.

I try not to abuse the Urgency level, but am I shooting myself in the foot by only selecting “Medium”?

image

SLA is within 4 business hours for cases that have a medium priority created from the portal. If it is more urgent than that, one can change the priority or call into the support line and speak with a person. For truly urgent issues that need to be addressed ASAP, one should always call into the support line.

To paraphrase Syndrome, if every case is urgent, then none of them are.

My point being is that people should set the priority appropriately based on their business needs so that we can allocate the appropriate level of resource to it.

Cases created via the portal may take a bit longer to get the first response with us trying to meet the defined SLA, but, the first response will be from an appropriate resource that can assist assuming all needed info is entered in the case during submission.

2 Likes

[quote=“aidacra, post:6, topic:48184”] … Cases created via the portal may take a bit longer to get the first response(with us trying to meet the defined SLA), but, the first response will be from an appropriate resource that can assist (assuming all needed info is entered in the case during submission).
[/quote]

This is why I like the portal.

For really urgent issues, usually make the case on the portal set to urgent and with all the details I think are needed ie: full error description, screen shots, etc then I call in so they can see the details. Hopefully that isn’t breaking any rules, it usually seems to help the techs I speak with.

2 Likes

You need to click on Quantum solution. It was solved here AND by support at the same time.

1 Like

Support provided by Kat Schrodinger.

Your problem is both simultaneously resolved and unresolved. Only after observing the results is the wave function collapsed, such that the state of resolution is determined.

5 Likes

Hello @aidacra. I opened a case with support with my ERP Analyzer health check results and requested advice on the proper procedures to address those. Here is the reply I received:
“This section can actually be ignored. We have been trying to get the dev team to remove it as it created confusion.”
I promise I’m not trying to get anyone in trouble. I just want to follow all the steps necessary to make our upgrade go as smoothly as possible.

I agree with Calvin that some of these are self-explanatory but others are a bit cryptic. For example, what is “script value”? And the selection criteria partnum <> “” doesn’t quite make sense to me.
Should I ignore these and move forward with my upgrade (10.1.400 to 10.2.400)?

Most look like they are about orphaned records, or ones with some minor inconsistancy.

But that 2nd one (“Update Part set partnum to script…”) is pretty cryptic, and something I’d want support to doubly confirm that it is not an issue.

I’d think that a finding that implies the PartNum of the part table, needs to be updated, is kind of something to worry about.

Hi ckrusen,

at last, what is the solution for 2nd one (“Update Part set partnum to script…”)?