Sage 100

Upgraded client SAGE 100 STD from v4.30 to v2015 PU#2 - Conversion went well except ALE Lookup for CI_Item is showing BLANK in Inventory, Purchase Order and Sales Order modules. I tried to follow the instruction in Knowledgebase Article #20379 and create the table ""CI_ITEM"". Did not work. Any ideas please?

Check that you don't have a blank first record in CI_Item.

We ran into this. Were there custom fields? If yes, the fix we did was going through Custom Office and exporting all the custom fields out, then reimported them. That fixed the issue. This was in a weird migration, so it might not apply, but worth mentioning!

@RobertaChase YES! the first record in my v2015 CI_Item.M4T file in blank. I went back and checked the v4.30 CI_Item.M4T file and the first record was also a blank code. So does this mean I need to delete the first record in v4.30 CI_Item.M4t and re-convert my Inventory files? @RhondaMcNamara No custom fields in any data files.

I believe all I did was copy the CI_Item folder in the current version (always have a BU) and then delete the bad record. Test the ALE. I've run into this a few times.

Michael - I've run into this a bunch too. Either DFDM whack the blank record in 4.30 or in the current version like Roberta said. At least you didn't run into the situation where the ItemType was blank in 50% of the records and the lookup was empty because of that. And RhondaMac next time just go to UDF Maintenance, add a quick UDF called ZTEMP, update it, then delete the UDF, update it. This will re-align the physical file to dictionary.

@AlnoorCassim I did whack the first record (it was blank) in the CI_Item.M4T file and my ALE Lookup did not work. Then I looked closer and NONE of my 5,490 converted CI_Item.M4T records have any fields populated with data except the ItemCode (first = key) field. What is the cure to re-convert from 4.30 to 5.20 PU#2 the CI_Item.M4T file? Will I need to reconvert all company files again or can I just convert the CI_Item.M4T file?

Michael it sounds like the dictionary is not in alignment with the CI_Item file in 4.30. What Rhonda Mac said may be applicable here that there may be extra fields. This would happen for example if you say swapped the client's ProvideX.dde and DDF files in the past or they had. I would try on 4.30 (making sure you have a backup of 4.30) either the UDF trick I mentioned earlier OR the embedded IO trick @JoanSerr mentions every now and then (search for it, run for at least the C/I module) Then you have to migrate and convert again ??

How to replace embedded IO files Possible Resolution: 1. On the File menu, click Run. 2. In the Program field, enter SYZCON 3. Click OK. 4. At the prompt, enter O=NEW(""SY_ACTIVATION_BUS"",%SYS_SS) 5. Press ENTER. 6. At the prompt, enter PRINT O'ACTIVATE(""y/y"",""xxx"") Notes: * y/y = module (for example: S/0, C/I, I/M, and so on) * xxx = company code * 1 is returned if the last command was successful * At the prompt, enter bye * Press ENTER.

Thank you @AlnoorCassim and @RobertWood and everyone else. I went back into v4.30 and deleted the CI_Item blank record. Then performed Robert's instructions to replace the C/I embedded IO files in v4.30. Re-migrated and re-converted the company data and the CI_Item.M4T file populated with the correct data. The client did have a Job Cost Extended Solution at one time but discontinued its use several versions before.