Sage 100

Client wants to know if VI can be designed so that an import looks at the current MAS company code and use it for validation. Example - import is run against ABC company -- Can I use perform logic to read in that current 3 character MAS code and then use it in validating against another field in the source input file. Something like --- If I'm importing into company ABC only import the lines where column 1 equals ABC (the company code passed in the import). I know this could probably work by creating separate VI jobs (one for each company) but the client wants to eliminate as much possibility for user error (and separate VI jobs would likely still require someone to choose the right job). If the answer is that perform logic could do this - then is there an example that you can share?

Are you importing into legacy or business framework modules?

Framework - AP

i remembered that GL imports has a company code field and assigns the code by using <CompanyCode>. I just tried using that specific code (assigned) in an AP import temp field and it pulled in the company code. Now, if you can somehow use it in the record selection, you'd be almost there.

Why not as a conditional? Temp1 = Company code per Bill, Temp2= Company code column of import file. Conditional of one of the import lines - Temp1 = Temp2

I may have to do more research on this. I've found that the Select in VI seems broken and because I was under deadline to deliver an import I never really looked past the KB entry or two which seemed to affirm the problem. So I did use the conditional and (though not on the company code) and one of the problems with conditional (unless I'm using it in the wrong place) is you get failed records which some users find confusing when trying to determine if the import is working. In this case I think conditional could work since the client would probably like to combine two or more company records in one import source file and let VI sort out which to take.

Thanks will try. Assume that all you did was use the <CompanyCode> variable in a temp computed field? Wonder if it also could be used in a conditional. I'll check into this. Thanks.

It should and if not you could use a Temp field populated with that in a conditional.

I struggled with that back a few years ago and finally gave up. Instead I created multiple imports chained together that ran against same database and hardcoded the logic on each to only import for that company. Not saying it can't be done, just beyond my limited skillset.

It may be cheaper (and easier) to just buy multi-company AP and import the company code from source file. Don't you have a DSD employee discount card?