Crystal oelincmt linked to ppordfil

[MacolaHelp]

Have you successfully linked the oelincmt field to the ppordfil? I'm trying to link header comment records to the appropriate work orders. I either get nothing or all header comments for all sales orders. I might have 4 PP orders linked to one sales order. I'm sure it is something really obvious I am missing, but I am feeling brain dead right now. If you've done it, give me a clue, please. I have had to write a subreport to get all info re salesperson & their demographic information into the work order, but have been stymied by the comments. I'm sure it is something really obvious, but am stumped. Thanks in advance for your help.

 

[dgillz]

I am assumming you are in a forced demand=pull environment so that the mfg_order_no field in the oeordlin_sql table is getting populated. Is that a safe assumption?

If so what about dependant pop orders? Do they come into play at all?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[MacolaHelp]

I have actually gotten the oelincmt in the report now doing what I want it to do, but I had to remove the notes/comments subreport on the ICR to be able to link in the oelincmt file. Since the notes/comments subreport was linked to pplincmt, maybe a left outer join was needed so both tables could be on the report? If my client ends up needing to use pp comments at some point in time, then I'll have to revisit the whole thing & figure out why, but for now I have temporarily solved it. And, yes, my items are pp/pull & the mfg order is in oeordlin & the source order # (sales order) is in the ppordfil. It's actually kind of a cool report. I just enter the appropriate sales order # & I get all the work orders to print for that SO. The only downside on using the crystal is that the order status doesn't update to P for printed, so the duplicate work order doesn't print unless you also print to file using the macola interface. I suppose one could write a little flex thing to deal with the file update.

 

[crystalreporting]

You are correct on the need for a left outer join whenever you are referencing Macola's comment tables. If you use an equal join (typically the default), then you would only get orders with comments. Generally, I prefer to use subreports for comments - just seems to make the report cleaner. Crystal Reports using non ODBC datasources (i.e. native drivers) MUST use subreports for this type of join as equal joins are the only option. I have a client that prints all of their POP orders using a single Crystal Report - they are a 100% forced demand pull environment, and EVERY item is a feature/option item. The work order lists the feature/options selected for each item via the IMORDBLD table. The Crystal report uses selection criteria on the order status of R. I created a very simple MSAccess form that has two buttons - the first runs the Crystal Report, and the second runs a SQL statement to update all R (released) orders to P (printed). This is the only area that is updated with Macola prints released POP orders as a separate step. I chose MSAccess as the client does not have flex, and I wanted them to be able to make changes to it in the future if need be.