Sage 100

I have a client on 2013 std that uses both customer and general aliases on the same items. They want to print only customer aliases on the order, invoice and pack slips. The problem as I see it is the alias type is not identified in sales order detail. There might be a case where the alias field is populated with a general alias because a customer alias does not exist for that customer and they want that to be suppressed. Does anyone have any ideas on how to do this?

You could link the IM_Alias table to the AR_Customer table by customer number. That way, only that customer's alias would print.

Can you add an alias type UDF to relevant work tables and source it from IM_Alias?

@GregStiles are you sure the Alias for the customer doesn't print? I think when you have one for the customer it will use that one first.

I could be wrong but I was under the impression that the Customer Alias will print on SO's and Invoices only if it's linked to that customer in Alias Maintenance. Same with Vendor Alias's for PO's

What if you define the type to be ""C"" customer, where as ""G"" is general

You would have to add the alias table

@ThereseLogeais I will try that, I think that may be the solution. Don't print the alias in the work table but create a link using Item Code + Customer Number to the alias table, if there is a customer alias, it will print, if there is no customer alias, it will not print. I do think that will work. @MarkKotyla , no I could not link to the alias table with a UDF @DianeRuth & @KennyDaniel the customer alias absolutely DOES print, it's the general aliases when a customer alias does not exist that are the problem.

Is it possible to append general alias items with ""_G""? Edit IM_Alias in Excel, initialize and import back in with changed general aliases? Then conditionally suppress if alias ends in _G?

There is another weird issue I saw - I think it was on 2014. User called and reported an issue **scanning** an alias if there is both a general and customer alias created for the same item. This user was able to scan everything normally but where there was both a customer and general alias the scan wouldn't work.

@MarkKotyla I thought of that too. I am going to try this morning to join the work table to the alias table by customer number and see how that goes. Your suggestion is my backup plan. @WayneSchulz hmmm, when there is both a general and a customer alias it does cause some interesting situations that Sage did not anticipate.

Linking directly to the item alias table using Item Code + AR Division + Customer Number was the solution. Thanks @ThereseLogeais

IS it a left outer join?

@MarkKotyla correct - a left outer join is required since there may not be corresponding record in the item Alias table.