Sage 100

VI Import to SO Invoice Entry with ASSIGN customer number and division I have set up VI imports to SO entry with a runtime assign of the customer number without issue. But now I am doing a VI to SO Invoice Entry with a hard assigned Customer number / Div. They are not part of the import file. However, the invoice number is part of the import file data. I get the message on the line records that the header is invalid. When I look at the header record, it shows the invoice number only, no customer ID. I'm ""assuming"" I can let the business logic apply the other things like default tax schedule, etc. Anything obvious I'm missing?

Are you using a temp file to do something with the customer # field?

What version???

temp field I mean. If so, you need to make sure it's set to Key assign.

Is batch entry turned on?

Version 2013 standard. Not using any temp files for the customer # field . Just made the customer number field an ASSIGN and hard coded the customer number. The import is for only one customer with about 150 lines.. Also - they provide the alias, so I'm again ""assuming"" that the business logic will cross reference the item number.

is the customer number assigned AFTER the invoice number? your not assigning a sales order number are you? I can't think of any other reasons

Ahh, batch entry. I'll check that...

Customer number assigned after invoice number. no sales order number assigned.

OK - solution 1: It was configured for batch entry - I assigned the batch ID and now the header works. Now the problem of linking alias (in import file) to the item number. Anyone have experience with that?

If the business logic isn't handling it, then I'm out. You might be able to set up a link to the alias table, I always use the VI Export to setup a custom table linking. The persist to the VI Import side but for a one time import, I'd probably link the Item # into the same source file externally and then import the invoice.

Getting closer. Note: learn to not believe the what the customer says, ""Yes, the UPC's are already in MAS as aliases"". Except, they aren't....

Well, dogone it, it's working! I like UPCs that aren't uniform, it makes life more interesting :) Thank you all for your help. It's good to have a support team available.