Defaulting comment on production work orders

[Prognewb]

We're having an issue with a comment defaulting onto our production work orders.
When printing a new production work order, the comment section defaults to the same comment for each order, and I can't find where to shut it off/change it.
When we enter a new production work order, the comment is being populated into the cmt column in the pplincmt_sql table, which is in a subreport on the MACPP04P1.rpt report.

It didn't always do this, it just recently started, so I'm not sure if it's a setting that someone was messing with, or if an update flipped a switch somewhere.

I have searched the net and other Macola resources I have and haven't found an answer. I hope I have given enough information, and any help would be appreciated. Thanks

 

[NEmacGuy]

Possible item to check:
Check in inventory under Note / Text or Item Note, Item number would be @@@@@@ should be six @ symbols.

 

[Prognewb]

Thanks, I hadn't thought of that, so I checked, but it isn't showing up there... it doesn't seem to be linked to any of the individual items, just showing up on the production work order no matter what items are on it.

 

[NEmacGuy]

Are you sure that it is in the pplincmt_sql table.

I would check the crystal report (has anyone changed it recently). Perhaps hard coded the note in the report by mistake ?

Any customizations? Tigger.....

If you are savy with crystal I would query your Item Notes file would be the natural method of having a note on file that automatically prints on a given document type.

Or perhaps you have a note stuck in a work file that copies to each new work order.

 

[stravis]

There are several possible sources of this comment.

1. The comment is coded in the the screen designer and you are creating production orders manually. If a different user is now creating your work orders this could account for the sudden addition of the comment.

2. Old code is coming in to play and is updating orders automatically. This could be a Flexibility solution, SQL Trigger, or ... solution. There may be some condition that causes the code to apply the comment that is now coming in to play.

3. A bug.

4. Other...

How are you creating your production orders now? The mechanism used to create your production orders is likely at the root of the situation.

Are you seeing one record in the pplincmt_sql table for each order or is there maybe a record in the table with a bad index? Macola sometimes links to records in tables that have a blank value in one of the indexed fields, such as the ord_no field.

Scott Travis

http://www.enterpriseexpressions.com