Change glactmst conversion from origin to i21

Issue No: GL-1939
Created 7/17/2015 7:42:07 AM
Type Feature
Priority Major
Status Closed
Resolution Fixed
Fixed Version 15.4
Description *ISSUE*   Recently we experience an issue with conversion where the primary account does not contain the same length.   When we modified the glactmst to a different length, all the origin master files such as control files, inventory files, etc. becomes invalid due to the structure change due to i21 requirements. We cannot change origin glactmst account structure during i21 conversion. We can continue to format i21 structure to our i21 current structure requirements, but modify the strExternalId and strCurrentExternalId in tblGLCOACrossRefence to match the external (origin) structure. The tblGLCOACrossRefence will be our gateway between i21 and external softwares.     To fix the customer:   * We restored glactmst back to its original structure * Modified tblGLCOACrossReference strExternalID and strCurrentExternalId to "match" the account setup in origin. I use term "match" loosely because the strExternalId and strCurrentExternalId are two different formats. We ensured that primary is appropriately referenced. * strExternalId 110000.00001007 * strCurrentExternalId 00110000-00001007 * Imported from Subledger and import was successful after modification of tblGLCOACrossReference *   *Solution*   Upon conversion:   - Prompt user of the duplicate primary codes.   - Allow the user to enter new primary code and be able to map it on one of the duplicates then continue COA conversion.   -Make sure tblGLCOACrossReference strExternalID and strCurrentExternalId will still match the Origin's original main account.